From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Santi B?jar <sbejar@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] git-what: explain what to do next
Date: Tue, 27 May 2008 15:52:59 +0200 [thread overview]
Message-ID: <20080527135259.GA12551@cuci.nl> (raw)
In-Reply-To: <8aa486160805270637m3fc640bfr9fa51eb917460e5c@mail.gmail.com>
Santi B?jar wrote:
>On Tue, May 27, 2008 at 3:12 PM, Johannes Schindelin
><Johannes.Schindelin@gmx.de> wrote:
>> Sure it is. But cluttering up the commands for something that is not
>> really proven to be wanted by many is IMO inferior.
>This is an argument against git-whatzzup.sh in general. Point taken.
Not really. It's an argument against cluttering up the existing core
with this stuff.
>Moreover, this could be integrated in "git status".
I personally have no need for such a thing, but in effect it is the git
commandline equivalent of MS-Office "Clippy", which provides a hands-on
tutorial in git while you are trying to use it (with the subtle yet
important difference that it only provides advice when called).
So if you'd keep it confined to a shell script externally from the core
commands, I could imagine a lot of new (or occasional) users of git being
rather happy with an "interactive manual/hands-on tutorial" like this.
--
Sincerely, srb@cuci.nl
Stephen R. van den Berg.
Skiing beyond this point may result in death and/or loss of skiing privileges.
next prev parent reply other threads:[~2008-05-27 13:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:34 [RFC/PATCH] git-what: explain what to do next Santi Béjar
2008-05-27 10:53 ` Johannes Schindelin
2008-05-27 12:58 ` Santi Béjar
2008-05-27 13:12 ` Johannes Schindelin
2008-05-27 13:37 ` Santi Béjar
2008-05-27 13:52 ` Stephen R. van den Berg [this message]
2008-05-27 14:21 ` Santi Béjar
2008-05-27 18:08 ` Steven Walter
2008-05-27 20:24 ` Junio C Hamano
2008-05-27 20:51 ` Junio C Hamano
2008-05-28 9:12 ` Santi Béjar
2008-05-29 4:39 ` Christian Couder
2008-05-29 5:09 ` Junio C Hamano
2008-05-29 14:56 ` Jon Loeliger
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=20080527135259.GA12551@cuci.nl \
--to=srb@cuci.nl \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sbejar@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).