Home | History | Annotate | Download | only in docs

Lines Matching full:commit

88 Preferably, each fix that corrects a problem should be in its own patch/commit
89 with its own description/commit message stating exactly what they correct so
153 git commit that is easy to merge and they are easy to track and not that easy
186 ### Write good commit messages
188 A short guide to how to write commit messages in the curl project.
203 Don't forget to use commit --author="" if you commit someone else's work, and
205 you commit
222 You then proceed and edit all the files you like and you commit them to your
225 git commit [file]
227 As usual, group your commits so that you commit all changes at once that
236 commit.