From: Jeff King <peff@peff.net>
Date: Sat, 20 Oct 2007 05:00:19 GMT
Subject: Re: [RFC/PATCH] git-fetch: mega-terse fetch output
Message-ID: <20071020050019.GA27282@coredump.intra.peff.net>
In-Reply-To: <alpine.LFD.0.9999.0710191009330.19446@xanadu.home>

On Fri, Oct 19, 2007 at 10:14:59AM -0400, Nicolas Pitre wrote:

> > ==> git://repo.or.cz/git/spearce.git
> >  * (new)              gitk -> spearce/gitk
> >  * 1aa3d01..e7187e4   maint -> spearce/maint
> >  * de61e42..7840ce6   master -> spearce/master
> >  * 895be02..2fe5433   next -> spearce/next
> >  + 89fa332...1e4c517  pu -> spearce/pu
> >  * (new)              todo -> spearce/todo
> 
> Actually I think this is the best format so far: one line per branch, no 
> terminal width issue (long branch names are simply wrapped), the 
> old..new info is there also with the single character marker to quickly 
> notice the type of update.

Technically speaking, the hash IDs can be up to 80 characters long,
since they are meant to be unique abbreviations. But in practice, I
think leaving enough space for 10 + '...' + 10 should accomodate just
about any project (IIRC, the kernel's longest non-unique is around 9).

-Peff