| commit | 8a93f9576a705753845ffa9fc5eb62c1d7fdd4a1 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Fri, 16 Mar 2012 14:48:33 +0000 (16 07:48 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 20 Mar 2012 20:30:30 +0000 (20 13:30 -0700) | ||
| tree | 1d11084b83fe578087240b6f26edb593c22fb8bb | treesnapshot (tar.gz zip) |
| parent | a99c5e5921fcb4fd003fd3424be4db649393731f | commitdiff |
rebase -i: remind that the lines are top-to-bottom
Nelson Benitez Leon opened a discussion with a patch with this in the
note:
Hi, I was using git rebase -i for some time now and never occured to
me I could reorder the commit lines to affect the order the commits
are applied, learnt that recently from a git tutorial.
Nelson's patch was to stress the fact that the lines in the insn sheet can
be re-ordered in a much more verbose way. Let's add a one-liner reminder
and also remind that the lines in the insn sheet is read from top to
bottom, unlike the "git log" output.
Discussion-triggered-by: Nelson Benitez Leon
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Nelson Benitez Leon opened a discussion with a patch with this in the
note:
Hi, I was using git rebase -i for some time now and never occured to
me I could reorder the commit lines to affect the order the commits
are applied, learnt that recently from a git tutorial.
Nelson's patch was to stress the fact that the lines in the insn sheet can
be re-ordered in a much more verbose way. Let's add a one-liner reminder
and also remind that the lines in the insn sheet is read from top to
bottom, unlike the "git log" output.
Discussion-triggered-by: Nelson Benitez Leon
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-rebase--interactive.sh | diffblobblamehistory |