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

Re: Reference for git.git release process

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 26, 2009, 03:13 UTC
Message-ID
<7vtz5hugc6.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20090326022757.GC5835@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Mirror mode would handle this automatically, but it unfortunately also
> ignores your push refspec. So any cruft or work-in-progress refs in your
> repository would be pushed.
Exactly.

Incidentally, that is why I usually favor the current 'matching' default. If I decide to push something to the other repository, the other repository remembers my wish, so I do not have to keep track (of course, for that to work effectively, you have to _own_ the other side; it does not work well for a shared public repository and that is why we had a lengthy discussion on push.default).

Previous: Jeff KingNext: Jeff King
Message 7 of 14 in “Reference for git.git release process”
  1. Raman GuptaMar 25, 2009
  2. Junio C HamanoMar 25, 2009
  3. Raman GuptaMar 25, 2009
  4. Junio C HamanoMar 25, 2009
  5. Junio C HamanoMar 26, 2009
  6. Jeff KingMar 26, 2009
  7. Junio C HamanoMar 26, 2009
  8. Jeff KingMar 26, 2009
  9. Junio C HamanoMar 26, 2009
  10. Jeff KingMar 26, 2009
  11. Junio C HamanoMar 26, 2009
  12. Shawn O. PearceMar 26, 2009
  13. Andreas EricssonMar 26, 2009
  14. Raman GuptaMar 26, 2009

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.