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

Re: [RFC/PATCH 0/3] tracking per-ref errors on push

From
Jeff King <peff@peff.net>
Date
Nov 13, 2007, 11:34 UTC
Message-ID
<20071113113437.GB15845@sigill.intra.peff.net>
In-Reply-To
<20071113102500.GA2767@sigill.intra.peff.net>
On Tue, Nov 13, 2007 at 05:25:01AM -0500, Jeff King wrote:
>   - It looks like the push mirror code just made it into next, which
>     is going to require a conflict-heavy rebase on my part.

This turned out not to be too bad. A rebased series (with the extra patch I just posted) follows, and it passes the test suite (though I still think more tests are in order).

-Peff
Previous: Jeff KingNext: Jeff King
Message 10 of 20 in “tracking per-ref errors on push”
  1. 0/3 tracking per-ref errors on pushJeff King, Nov 13, 2007
  2. 1/3 send-pack: track errors for each refJeff King, Nov 13, 2007
  3. Jeff KingNov 13, 2007
  4. Alex RiesenNov 13, 2007
  5. Jeff KingNov 13, 2007
  6. Alex RiesenNov 13, 2007
  7. 2/3 send-pack: check ref->status before updating tracking refsJeff King, Nov 13, 2007
  8. 3/3 send-pack: assign remote errors to each refJeff King, Nov 13, 2007
  9. Jeff KingNov 13, 2007
  10. Jeff KingNov 13, 2007
  11. 1/3 send-pack: track errors for each refJeff King, Nov 13, 2007
  12. 2/3 send-pack: check ref->status before updating tracking refsJeff King, Nov 13, 2007
  13. 3/3 send-pack: assign remote errors to each refJeff King, Nov 13, 2007
  14. Junio C HamanoNov 14, 2007
  15. Junio C HamanoNov 14, 2007
  16. Johannes SchindelinNov 14, 2007
  17. Junio C HamanoNov 14, 2007
  18. Jeff KingNov 15, 2007
  19. Junio C HamanoNov 16, 2007
  20. Jeff KingNov 15, 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.