From: Junio C Hamano <gitster@pobox.com>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH] git-fetch: more terse fetch output
Date: Fri, 02 Nov 2007 22:36:04 -0700 [thread overview]
Message-ID: <7vtzo3yjp7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711030101340.21255@xanadu.home> (Nicolas Pitre's message of "Sat, 03 Nov 2007 01:32:48 -0400 (EDT)")
Nicolas Pitre <nico@cam.org> writes:
> This makes the fetch output much more terse and prettier on a 80 column
> display, based on a consensus reached on the mailing list. Here's an
> example output:
>
> Receiving objects: 100% (5439/5439), 1.60 MiB | 636 KiB/s, done.
> Resolving deltas: 100% (4604/4604), done.
> From git://git.kernel.org/pub/scm/git/git
> ! [rejected] html -> origin/html (non fast forward)
> 136e631..f45e867 maint -> origin/maint (fast forward)
> 9850e2e..44dd7e0 man -> origin/man (fast forward)
> 3e4bb08..e3d6d56 master -> origin/master (fast forward)
> fa3665c..536f64a next -> origin/next (fast forward)
> + 4f6d9d6...768326f pu -> origin/pu (forced update)
> * [new branch] todo -> origin/todo
Yay!
next prev parent reply other threads:[~2007-11-03 5:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 5:32 [PATCH] git-fetch: more terse fetch output Nicolas Pitre
2007-11-03 5:36 ` Junio C Hamano [this message]
2007-11-03 19:34 ` Linus Torvalds
2007-11-03 20:30 ` Nicolas Pitre
2007-11-03 20:40 ` Mike Hommey
2007-11-03 20:50 ` Nicolas Pitre
2007-11-03 21:03 ` Mike Hommey
2007-11-03 21:46 ` Pierre Habouzit
2007-11-03 22:02 ` Jakub Narebski
2007-11-03 22:48 ` Linus Torvalds
2007-11-03 23:31 ` Mike Hommey
2007-11-04 0:54 ` Johannes Schindelin
2007-11-04 1:03 ` Junio C Hamano
2007-11-04 1:49 ` David Brown
2007-11-04 2:14 ` Robin Rosenberg
2007-11-03 22:45 ` Linus Torvalds
2007-11-04 9:56 ` Steffen Prohaska
2007-11-04 4:58 ` Jeff King
2007-11-04 13:13 ` Johannes Schindelin
2007-11-04 14:01 ` Pierre Habouzit
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=7vtzo3yjp7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=peff@peff.net \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.