Lines Matching refs:commit
104 staged for the next commit, and usually some useful information about
109 Your branch is ahead of 'origin/blead' by 1 commit.
116 Changes not staged for commit:
128 This shows that there were changes to this document staged for commit,
132 shows that there is one commit on the working branch C<blead> which has
135 C<git commit>.
202 Now commit your change locally:
204 % git commit -a -m 'Rename Leon Brocard to Orange Brocard'
205 Created commit 6196c1d: Rename Leon Brocard to Orange Brocard
209 have changed. If at this time, you only want to commit some of the
211 C<S<git add I<FILE ...>>> before doing the commit. C<S<git add
212 --interactive>> allows you to even just commit portions of files
215 The C<-m> option is used to specify the commit message. If you omit it,
219 first line of the commit message doesn't exceed the 50 character legal
221 makes a good commit message.
223 Once you've finished writing your commit message and exited your
227 Created commit daf8e63: explain git status and stuff about remotes
239 nothing added to commit but untracked files present (use "git add" to
246 You can examine your last commit with:
253 % git commit -a --amend
327 C<git> provides a built-in way to determine which commit should be blamed
329 history to locate the first failing commit. It is fast, powerful and
350 Which commit caused this example code to break?
354 Which commit caused this example code to start working?
358 Which commit added the first file to match this regex?
362 Which commit removed the last file to match this regex?
392 This results in checking out the median commit between C<HEAD> and
397 When the first bad commit is isolated, C<git bisect> will tell you so:
399 ca4cfd28534303b82a216cfe83a1c80cbc3b9dc5 is first bad commit
400 commit ca4cfd28534303b82a216cfe83a1c80cbc3b9dc5
414 first C<bad> state. If you want to search for the commit that I<solved>
417 upper as C<bad>. The "first bad commit" has then to be understood as
418 the "first commit where the bug is solved".
426 you may be able to patch the source code at the older commit point. To
455 Sometimes, an author might have found an error in an early commit which
498 maint-* branches. If a typo (or worse) sneaks into a commit to blead or
499 maint-*, we'll fix it in another commit. The only types of updates
636 % git commit -a -m "Some fixing" \
642 commit b1b3dab48344cff6de4087efca3dbd63548ab5e2
691 Make sure you have a good commit message. See L<perlhack/Commit
752 commit. You should perform your work on a L<topic branch|/Topic
757 commit on blead, but a final rebase makes the history linear
768 % git merge --no-ff --no-commit committer/somework
769 % git commit -a
772 if all your work can be applied linearly against blead, a merge commit
775 by the merge commit.
777 C<--no-commit> means that the merge commit will be I<prepared> but not
778 I<committed>. The commit is then actually performed when you run the
779 next command, which will bring up your editor to describe the commit.
780 Without C<--no-commit>, the commit would be made with nearly no useful
781 message, which would greatly diminish the value of the merge commit as a
784 When describing the merge commit, explain the purpose of the branch, and
797 then your carefully created merge commit will be lost! To avoid this you
803 This will recreate your merge commit.
814 To commit to a maintenance version of perl, you need to create a local
820 remote branch C<origin/maint-5.005>. Then you can pull, commit, merge
826 original commit in the new commit message.
835 on other OSes test the change before you commit it to blead.
851 Make some changes, build perl and test your changes, then commit them to
879 then you should prepare a merge commit in which to give an overview of
883 % git merge win32stat --no-ff --no-commit