From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jon Loeliger <jdl@freescale.com>
Cc: Jakub Narebski <jnareb@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Deprecate git-fetch-pack?
Date: Mon, 12 Nov 2007 19:08:51 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711121905300.4362@racer.site> (raw)
In-Reply-To: <1194893799.1335.4.camel@ld0161-tx32>
Hi,
On Mon, 12 Nov 2007, Jon Loeliger wrote:
> On Mon, 2007-11-12 at 11:33, Johannes Schindelin wrote:
>
> > Jon wrote:
> >
> > > It [git show-branch] is a very useful command, and usable on systems
> > > where GUI isn't an option.
> >
> > Yes, and those systems are the majority nowadays. Oh, wait...
>
> I remotely log into my server machines frequently.
Okay, sorry. I was in a bad mood (you know why, I guess), and I was a
little tongue-in-cheek here. I apologise.
The thing is, show-branch might be mighty useful for you, but I agree with
another poster that its output is not for the faint of heart, if it goes
without an explanation.
So I vote for keeping relatively quiet about it in the output of "git
help" which is -- according to some people -- the first thing new git
users see.
Power users, such as yourself, will read in the user manual or in the FAQ
about the existence of this nice tool, and do not need to be reminded of
it by git-help.
Fair enough?
Dscho
next prev parent reply other threads:[~2007-11-12 19:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 23:11 Deprecate git-fetch-pack? Daniel Barkalow
2007-11-11 0:48 ` Junio C Hamano
2007-11-11 3:09 ` Ask Bjørn Hansen
2007-11-11 11:05 ` Johannes Schindelin
2007-11-11 21:16 ` Junio C Hamano
2007-11-11 22:21 ` Theodore Tso
2007-11-11 22:35 ` Junio C Hamano
2007-11-11 22:50 ` Johannes Schindelin
2007-11-11 23:58 ` Theodore Tso
2007-11-12 0:16 ` Jakub Narebski
2007-11-12 17:29 ` Jon Loeliger
2007-11-12 17:33 ` Johannes Schindelin
2007-11-12 18:56 ` Jon Loeliger
2007-11-12 19:08 ` Johannes Schindelin [this message]
2007-11-12 19:16 ` Jon Loeliger
2007-11-12 0:57 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Theodore Ts'o
2007-11-12 0:57 ` [PATCH,RFC 2/2] Remove hint to use "git help -a" Theodore Ts'o
2007-11-12 2:21 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Junio C Hamano
2007-11-12 5:48 ` Ping Yin
2007-11-12 6:22 ` Theodore Tso
2007-11-12 7:26 ` Junio C Hamano
2007-11-12 10:24 ` Mike Hommey
2007-11-12 12:23 ` Johannes Schindelin
2007-11-12 7:57 ` Ask Bjørn Hansen
2007-11-12 10:21 ` Andreas Ericsson
2007-11-12 15:20 ` Theodore Tso
2007-11-12 10:15 ` Deprecate git-fetch-pack? Andreas Ericsson
2007-11-12 1:10 ` Ask Bjørn Hansen
2007-11-11 8:32 ` Mike Hommey
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=Pine.LNX.4.64.0711121905300.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.com \
--cc=jnareb@gmail.com \
/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).