git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <sbejar@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
	"Theodore Tso" <tytso@thunk.org>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	"David Symonds" <dsymonds@gmail.com>, "Jeff King" <peff@peff.net>,
	git@vger.kernel.org
Subject: Re: [RFC/PATCH] git-fetch: mega-terse fetch output
Date: Fri, 19 Oct 2007 16:31:08 +0200	[thread overview]
Message-ID: <8aa486160710190731v67626fd8wa94ba069a17f73ce@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710191009330.19446@xanadu.home>

On 10/19/07, Nicolas Pitre <nico@cam.org> wrote:
> On Fri, 19 Oct 2007, Johannes Sixt wrote:
>
> > Theodore Tso schrieb:
> > > ==> git://repo.or.cz/git/spearce.git
> > >  * branch gitk -> spearce/gitk              (new)
> > >  * branch maint -> spearce/maint    1aa3d01..e7187e4
> > >  * branch master -> spearce/master  de61e42..7840ce6
> > >  * branch next -> spearce/next              895be02..2fe5433
> > >  + branch pu -> spearce/pu          89fa332...1e4c517
> > >  * branch todo -> spearce/todo              (new)
> >
> > > As far as the padding, it would be a pain to figure out how to make
> > > the right hand column be padded so that it starts 3 spaces after the
> > > longest "  * branch foo -> bar" line, but that would look the best.
> >
> > But this way it wouldn't be difficult at all:
> >
> > ==> 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.

I like it too. I would like to add some more descripton, because I
think for newbies the .. and ... can be overlooked. Something like:

$ git fetch spearce
...
URL: git://repo.or.cz/git/spearce.git
 * (new)              spearce/gitk: new branch 'gitk'
 * 1aa3d01..e7187e4   spearce/maint: fast forward to branch 'maint'
 * de61e42..7840ce6   spearce/master: fast forward to branch 'master'
 * 895be02..2fe5433   spearce/next: fast forward to branch 'next'
 + 89fa332...1e4c517  spearce/pu: forcing update to non-fast forward branch 'pu'
 * (new)              spearce/todo: new branch spearce/todo

I would also put 'URL:' instead '==>'.

Santi

  parent reply	other threads:[~2007-10-19 14:31 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  6:22 [RFC/PATCH] git-fetch: mega-terse fetch output Jeff King
2007-10-19  6:39 ` David Symonds
2007-10-19  6:46   ` Jeff King
2007-10-19  7:39   ` Shawn O. Pearce
2007-10-19  7:57     ` Jeff King
2007-10-19  8:07       ` Shawn O. Pearce
2007-10-19  8:11         ` Jeff King
     [not found]         ` <?= =?ISO-8859-1?Q?2007101=049081127.?= =?ISO-8859-1?Q?GA30168@coredump?= =?ISO-8859-1?Q?.intra.peff.net>
2007-10-19  8:19           ` David Kastrup
2007-10-19  8:39             ` Jeff King
2007-10-19  8:21     ` Johannes Sixt
2007-10-19 10:03     ` Santi Béjar
2007-10-19 11:38       ` Theodore Tso
2007-10-19 12:31         ` Johannes Sixt
2007-10-19 14:14           ` Nicolas Pitre
2007-10-19 14:31             ` Johannes Schindelin
2007-10-19 14:31             ` Santi Béjar [this message]
2007-10-19 14:40               ` Karl Hasselström
2007-10-19 14:40               ` Johannes Sixt
2007-10-19 14:54                 ` Nicolas Pitre
2007-10-19 14:41               ` Johannes Schindelin
2007-10-19 14:56                 ` Nicolas Pitre
2007-10-19 14:52               ` Nicolas Pitre
2007-10-20  5:00             ` Jeff King
2007-10-20  6:58               ` Shawn O. Pearce
2007-10-19 14:38         ` Karl Hasselström
2007-10-19 15:03           ` Nicolas Pitre
2007-10-19 21:17             ` Theodore Tso
2007-10-19 21:40               ` Nicolas Pitre
2007-10-19 21:58                 ` Theodore Tso
2007-10-19 13:15       ` Nicolas Pitre
2007-10-23  8:39         ` Miles Bader
2007-10-19 10:45     ` Andreas Ericsson
2007-10-19 10:51     ` Andreas Ericsson
2007-10-19 13:05     ` Nicolas Pitre
2007-10-19 15:50     ` Steven Grimm
2007-10-19 15:53       ` Steven Grimm
2007-10-19 16:12       ` Nicolas Pitre
2007-10-19 17:26         ` Sam Ravnborg
2007-10-19 18:51           ` Nicolas Pitre
2007-10-19 10:40 ` Andreas Ericsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8aa486160710190731v67626fd8wa94ba069a17f73ce@mail.gmail.com \
    --to=sbejar@gmail.com \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=nico@cam.org \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    --cc=tytso@thunk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).