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

Re: Reference for git.git release process

From
Jeff King <peff@peff.net>
Date
Mar 26, 2009, 03:49 UTC
Message-ID
<20090326034909.GB8031@coredump.intra.peff.net>
In-Reply-To
<7v8wmtufn4.fsf@gitster.siamese.dyndns.org>
On Wed, Mar 25, 2009 at 08:28:15PM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> > So if I understand correctly, you would actually like "push matching,
> > delete missing" behavior?
> 
> Hmm, that would be good.  That would allow me to start publishing the
> individual topics with ease.
> 
> I never thought of that.

I'm not sure of the best way to implement it. Is it a new behavior on par with matching, tracking, current, etc; or is "delete missing" orthogonal to what is being pushed? Should "delete missing" attempt to match according to your refspecs, or according to the whole repo (like mirror)?

I was thinking "orthogonal, limited to your refspec". So configure via
  git config remote.origin.prune-push true
and then you can
  # pseudo-mirror following your refspec or matching behavior
  git push origin
  # push foo if it exists, or delete it if it doesn't
  git push origin foo
  # sync some subset of your refs
  git push origin refs/heads/jk/*:refs/heads/jk/*
-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 10 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.