"W. Trevor King" <wk...@tremily.us> writes:
> On Sun, Feb 17, 2013 at 06:23:11PM -0800, Junio C Hamano wrote:
>> "W. Trevor King" <wk...@tremily.us> writes:
>> > [[rewriting-one-commit]]
>> > Rewriting a single commit
>> > -------------------------
>> > @@ -2552,71 +2558,81 @@ $ git commit --amend
>> > which will replace the old commit by a new commit incorporating your
>> > changes, giving you a chance to edit the old commit message first.
>> ... A lot of lines removed here ...
>> > +[[reordering-patch-series]]
>> This change makes the [[rewriting-one-commit]] section say "We
>> already saw you can do 'commit --amend'" and nothing else. It makes
>> me wonder if the remaining section is worth keeping if we go this
> I think there should be some mention of `commit --amend` in the
> rewriting history section. It's a pretty straightforward idea though,
> so there's not all that much to say about it ;).
I do think teaching "commit --amend", "rebase" and "rebase -i"
together makes sense. It just felt that the remaining piece on
"commit --amend" looked too thin in the substance, but it may be a
good change in the existing flow of text.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html