From: Santi Béjar Date: Tue, 27 May 2008 14:21:04 GMT Subject: Re: [RFC/PATCH] git-what: explain what to do next Message-ID: <8aa486160805270721q64dff3f0gfbb9eb5384db027d@mail.gmail.com> In-Reply-To: <20080527135259.GA12551@cuci.nl> On Tue, May 27, 2008 at 3:52 PM, Stephen R. van den Berg wrote: > Santi B?jar wrote: >>On Tue, May 27, 2008 at 3:12 PM, Johannes Schindelin >> 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. Ok. I misunderstood it, sorry. > >>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). I don't have experience with Clippy, but my git-what.sh was just showing the help as shown before (well, actually not for bisect but is easy to fix). It is not a hands-on tutorial, it is more of "in which state (merging, bisecting,...) is my working tree, if it is in the middle of a complex process (bisect, merge, rebase,...) tell me what was the help message". It is not that different from the output of "git status", but for states. Santi