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

Re: [PATCH 0/3] more terse push output

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 5, 2007, 21:14 UTC
Message-ID
<7v7ikwpf7g.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20071105050517.GA6244@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
>   - the 'ref is not up-to-date, maybe you need to push' message has gone
>     away in favor of the terse '[rejected] ... (non-fast forward)'. I
>     know there was some discussion recently of enhancing that message.
>     Is this perhaps too terse?
I kind of like this part.

I also like the part that stops mentioning the "pretend fetching back" action. This would mostly parrot the same set of refs for people who do use the tracking branches anyway.

Previous: Steffen Prohaska
Message 6 of 6 in “more terse push output”
  1. 0/3 more terse push outputJeff King, Nov 5, 2007
  2. 1/3 more terse push outputJeff King, Nov 5, 2007
  3. 2/3 receive-pack: don't mention successful updatesJeff King, Nov 5, 2007
  4. 3/3 send-pack: require --verbose to show update of tracking refsJeff King, Nov 5, 2007
  5. Steffen ProhaskaNov 5, 2007
  6. Junio C HamanoNov 5, 2007

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.