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

Re: Keeping a non-1:1 mirror in sync and keeping private branches

From
Jeff King <peff@peff.net>
Date
Jul 16, 2017, 10:10 UTC
Message-ID
<20170716101045.aslfct7g5vqfqnhi@sigill.intra.peff.net>
In-Reply-To
<699d0274-285f-3d30-654d-d9ca59fe4dce@gmail.com>
On Sun, Jul 16, 2017 at 02:59:23AM +0200, Jan Danielsson wrote:
>    This seems to accomplish everything I want except that the the "git
> push" deletes any branches I have created on my self-hosted
> repository.
A mirrored push is basically:
  - push all refs, i.e., a "+refs/*:refs/*" refspec
  - enable --prune, to delete any branches that don't exist on the local
    side

But you can do those two things separately if you like. So your options are either:

  1. Drop the pruning (in which case deleted branches from the sync may
     accumulate, but depending on the patterns that may or may not be a
     problem).
  2. Use two different namespaces for the synced branches and the
     private ones (e.g., refs/mirror/* in addition to your branches in
     refs/heads/*). The obvious downside is that anybody cloning your
     downstream mirror doesn't pick up refs/mirror unless they configure
     that refspec explicitly.
-Peff
Previous: Jan DanielssonNext: Jan Danielsson
Message 2 of 4 in “Keeping a non-1:1 mirror in sync and keeping private branches”
  1. Jan DanielssonJul 16, 2017
  2. Jeff KingJul 16, 2017
  3. Jan DanielssonJul 16, 2017
  4. Jeff KingJul 16, 2017

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.