[PATCH] summary: Clarify output for the commit summary

Matt Mackall mpm at selenic.com
Mon Oct 19 16:05:25 CDT 2009


On Mon, 2009-10-19 at 22:20 +0200, Martin Geisler wrote:
> Matt Mackall <mpm at selenic.com> writes:
> 
> > On Mon, 2009-10-19 at 15:04 +0200, Martin Geisler wrote:
> >> David Soria Parra <sn_ at gmx.net> writes:
> >> 
> >> > # HG changeset patch
> >> > # User David Soria Parra <dsp at php.net>
> >> > # Date 1255929284 -7200
> >> > # Node ID 5b6db7d1461863da7014d2c46f8304b893b39282
> >> > # Parent  220d39af2e5779879dd9a7bf3af41d787b7ef9b6
> >> > summary: Clarify output for the commit summary
> >> 
> >> Thanks -- I added the 'files' part to all the labels instead and
> >> pushed this as d097bc2d1945, which I hope you don't mind.
> >> 
> >> Feel free to complain if you think this is too much output -- I
> >> normally only have some modified and some unknown files in my clones,
> >> so it's still pretty short for me. But perhaps others have other
> >> expectations?
> >
> > I think it's too much output. Again, extremely popular command ->
> > brevity. Compare:
> >
> > commit: 1 modified files, 1 addeded files, 1 removed files, 1 deleted
> > files, 1 unknown files, 1 unresolved files (new branch head)
> >
> > commit: 1 modified, 1 addeded, 1 removed, 1 deleted, 1 unknown, 1
> > unresolved (new branch head)
> 
> Well, are they not both output too long? :-)

Yes, the above is the worst case for both. Most of the time we'll have
just one line of output without 'files'.

-- 
http://selenic.com : development and support for Mercurial and Linux




More information about the Mercurial-devel mailing list