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

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

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 27, 2008, 10:53 UTC
Message-ID
<alpine.DEB.1.00.0805271151430.30431@racer>
In-Reply-To
<1211877299-27255-1-git-send-email-sbejar@gmail.com>
Hi,
On Tue, 27 May 2008, Santi Béjar wrote:
> In case you don't know the next step, if it is "git commit",
> "git commit --amend", "git rebase --continue" or something else.

We had a patch similar to this already, but I think that the right approach is _not_ to teach the single commands to explain their state, but to make a new script guessing the current state. AFAIR we have something like that in the completions already, as an (optional) prompt.

However, I think it would make sense to push for that .dotest,.git/.dotest-merge -> .git/rebase change _before_ having anything like git-whazzup.sh.

Ciao, Dscho

Previous: Santi BéjarNext: Santi Béjar
Message 2 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.