From: David Symonds Date: Fri, 19 Oct 2007 06:39:56 GMT Subject: Re: [RFC/PATCH] git-fetch: mega-terse fetch output Message-ID: In-Reply-To: <20071019062219.GA28499@coredump.intra.peff.net> On 19/10/2007, Jeff King wrote: > This makes the fetch output much more terse. It is likely to > be very controversial. Here's an example of the new output: > > Indexing objects: 100% (1061/1061), done. > Resolving deltas: 100% (638/638), done. > ==> git://repo.or.cz/git/spearce.git > * branch gitk -> origin/gitk > * branch maint -> origin/maint (fast forward) > * branch master -> origin/master (fast forward) > * branch next -> origin/next (fast forward) > - branch pu -> origin/pu (non-fast forward, refused) > * branch todo -> origin/todo (fast forward) > ==> git://repo.or.cz/git/spearce.git > * tag v1.5.3.2 -> v1.5.3.2 What about making it even more terse so it's even easier to visually scan: (mainly thinking that fast-forwarding is so common it could be considered the "default") > ==> git://repo.or.cz/git/spearce.git * gitk -> origin/gitk (new) * maint -> origin/maint * master -> origin/master * next -> origin/next - pu -> origin/pu (refused) * todo -> origin/todo ==> git://repo.or.cz/git/spearce.git * tag v1.5.3.2 Also, perhaps the trailing notes (fast forward, refused, etc.) should be significantly indented to the right to stand out even further from branch names that might be quite long. Dave.