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

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

From
Steven Walter <stevenrwalter@gmail.com>
Date
May 27, 2008, 18:08 UTC
Message-ID
<e06498070805271108t66a45abfy9abb5ed065e59e35@mail.gmail.com>
In-Reply-To
<8aa486160805270721q64dff3f0gfbb9eb5384db027d@mail.gmail.com>
On Tue, May 27, 2008 at 10:21 AM, Santi Béjar <sbejar@gmail.com> wrote:
Show 6 quoted lines
> On Tue, May 27, 2008 at 3:52 PM, Stephen R. van den Berg <srb@cuci.nl> wrote:
>> 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.
WANT.
>>>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.

The only changes I saw were to porcelain, not plumbing (or is this not what you mean by "core?") I see no problem with making the plumbing more user-friendly. That is really the only point of the porcelain. If you don't want user-friendly, use the plumbing directly.

Show 5 quoted lines
> 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.

Surely it has happened to everyone that you start a rebase, walk away and then continue hacking and committing with the rebase still in progress. It isn't too bad for an experienced user to recover from this state, but prevention is much better than cure. A simple "git what" command that could remind you of what you were doing would be a welcome addition, in my mind.

-- 
-Steven Walter <stevenrwalter@gmail.com>
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects."
 -Robert Heinlein
Previous: Santi BéjarNext: Junio C Hamano
Message 8 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.