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

Re: a more helpful message on "git status" output

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 18, 2014, 21:05 UTC
Message-ID
<20140718210500.GU12427@google.com>
In-Reply-To
<CAKQhN+p5FpX-GEZeX0t-Y1Sq6+fdfRpE+ACqhKgdLWGFRj0ToA@mail.gmail.com>
Julián Landerreche wrote:
> A more verbose, educational output could read:
>
>   (use "git pull" to fetch newer commits from upstream and update your local branch)
>   (use "git merge" to update your local branch)
Yes, I like this idea, with a few qualifications:
 1. The first line is long.  Is there a shorter way to say the same
    thing?  Maybe
    (use "git pull" to fetch newer commits and update your local branch)
 2. s/from upstream/from $remote/ (e.g., "from origin") in the first
    line?  Though that would make problem (1) worse.
 3. Is there some way to make it more obvious these two hints are
    independent suggestions and that the user doesn't need to do both?
    Maybe something as simple as
    (or use "git merge" to update your local branch)
 4. Should the advice differ based on whether the current branch is set
    up for merging or rebasing?

Thanks, Jonathan

Previous: Julián LanderrecheNext: Junio C Hamano
Message 4 of 6 in “a more helpful message on "git status" output”
  1. Julián LanderrecheJul 18, 2014
  2. Junio C HamanoJul 18, 2014
  3. Julián LanderrecheJul 18, 2014
  4. Jonathan NiederJul 18, 2014
  5. Junio C HamanoJul 18, 2014
  6. Matthieu MoyJul 21, 2014

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.