git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH] git-what: explain what to do next

From
SBSanti Béjar <sbejar@gmail.com>
Date
May 27, 2008, 14:21 UTC
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 <srb@cuci.nl> wrote:
Show 10 quoted lines
> 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.
Ok. I misunderstood it, sorry.
Show 7 quoted lines
>
>>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
Previous: Stephen R. van den BergNext: Steven Walter
Message 7 of 14 in “git-what: explain what to do next”
  1. git-what: explain what to do nextSanti Béjar, May 27, 2008
  2. Johannes SchindelinMay 27, 2008
  3. Santi BéjarMay 27, 2008
  4. Johannes SchindelinMay 27, 2008
  5. Santi BéjarMay 27, 2008
  6. Stephen R. van den BergMay 27, 2008
  7. Santi BéjarMay 27, 2008
  8. Steven WalterMay 27, 2008
  9. Junio C HamanoMay 27, 2008
  10. Junio C HamanoMay 27, 2008
  11. Santi BéjarMay 28, 2008
  12. Christian CouderMay 29, 2008
  13. Junio C HamanoMay 29, 2008
  14. Jon LoeligerMay 29, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.