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

Re: [PATCH 1/2] send-pack: cluster ref status reporting

From
Jeff King <peff@peff.net>
Date
Nov 21, 2007, 07:39 UTC
Message-ID
<20071121073938.GB10742@sigill.intra.peff.net>
In-Reply-To
<7vwsscgie2.fsf@gitster.siamese.dyndns.org>
On Tue, Nov 20, 2007 at 11:36:05PM -0800, Junio C Hamano wrote:
> Heh, at least I've privately queued it at the tip of
> jk/send-pack for review but not merged it to 'next' yet, after
> fixing it up (the last round I also fixed up so that was partly
> why I noticed -- the patch did not apply).

OK, good. I should have noticed because I also ran across the same patch failure when I did a rebase earlier today, but I didn't consider that the mistake had slipped out of my repo. :) Sorry for the confusion.

> The idea feels sound, and code under cursory look was fine.

I think it is probably worth applying then. It is slightly more useful to the user, and I haven't been able to see any downside.

-Peff
Previous: Junio C HamanoNext: Jeff King
Message 16 of 19 in “! [rejected] master -> master (non-fast forward)”
  1. Jon SmirlNov 18, 2007
  2. Junio C HamanoNov 18, 2007
  3. Jon SmirlNov 18, 2007
  4. Catalin MarinasNov 19, 2007
  5. Jon SmirlNov 19, 2007
  6. Daniel BarkalowNov 20, 2007
  7. Alex RiesenNov 18, 2007
  8. Jeff KingNov 20, 2007
  9. Alex RiesenNov 20, 2007
  10. Jeff KingNov 20, 2007
  11. 1/2 send-pack: cluster ref status reportingJeff King, Nov 20, 2007
  12. Alex RiesenNov 20, 2007
  13. Junio C HamanoNov 21, 2007
  14. Jeff KingNov 21, 2007
  15. Junio C HamanoNov 21, 2007
  16. Jeff KingNov 21, 2007
  17. Jeff KingNov 21, 2007
  18. 2/2 send-pack: print "maybe you need to pull" hintJeff King, Nov 20, 2007
  19. Alex RiesenNov 20, 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.