Re: Comments on "status -v"
- From
Junio C Hamano <junkio@cox.net>
- Date
- Feb 10, 2006, 22:12 UTC
- Message-ID
- <7v7j82vp6i.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <Pine.LNX.4.64.0602101333570.19172@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> I think I agree. Especially if doing "git commit -v", the _top_ of the > status message is what you'd normally be most aware of. I think.
Well the exactly same reasoning on my part, who keeps tons of untracked files in his repository, left the patch output there. Otherwise I have to scroll off a long "untracked files" list to get to the patch ;-).
But even with that gripe, I'd agree that patch at the end would be a better choice. The user asked for a patch so she wouldn't fail to see it even if many '#' lines precede the patch. With the current ordering, '#' lines will most likely be ignored.