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

Re: [PATCH] Add suggestion to hard-to-understand error message

From
Junio C Hamano <junkio@cox.net>
Date
Dec 22, 2005, 19:27 UTC
Message-ID
<7vek45lyor.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<43AA79EB.6040800@op5.se>
Andreas Ericsson <ae@op5.se> writes:
Show 9 quoted lines
> Junio C Hamano wrote:
>> In a sense, both are "pull first?" situation, and it probably is
>> more confusing to give different messages to the user in these
>> two cases.  From the end-user point of view they are the same
>> "remote is not strict subset.".
>
> In non-git'ish, does this mean "you're not up to date, so pull before 
> pushing" ? If so, why not say so? I'm sure it could prevent a fair few 
> problems for users (not least those new to scm's).

Perhaps. I was suggesting to say that in *both* places, not just one.

Previous: Andreas EricssonNext: Junio C Hamano
Message 4 of 7 in “Add suggestion to hard-to-understand error message”
  1. Add suggestion to hard-to-understand error messageJohannes Schindelin, Dec 21, 2005
  2. Junio C HamanoDec 22, 2005
  3. Andreas EricssonDec 22, 2005
  4. Junio C HamanoDec 22, 2005
  5. send-pack: reword non-fast-forward error message.Junio C Hamano, Dec 22, 2005
  6. Johannes SchindelinDec 22, 2005
  7. Andreas EricssonDec 23, 2005

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.