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

Re: mirror git repos: rsync vs. --mirror

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Mar 31, 2010, 01:44 UTC
Message-ID
<t2r2e24e5b91003301844i6ea98c92j6dba55d916c841f5@mail.gmail.com>
In-Reply-To
<3a75d1efc7cf125d84b8e02b7dabf7aa@212.159.54.234>

On Wed, Mar 31, 2010 at 3:30 AM, Julian Phillips <julian@quantumfyre.co.uk> wrote:

> On Tue, 30 Mar 2010 20:54:09 +0000, "Robin H. Johnson"
> <robbat2@gentoo.org>
>> git clone --mirror && git fetch:
>> Caveats:
>> - Branches and tags deleted in master persist in slaves :-(
> I don't think that fetch can do it, but "git remote prune origin" will.

as of 1.7 at least, fetch has --prune, and I tested it yesterday when someone (same person?) asked this on #git

Previous: Julian PhillipsNext: Robin H. Johnson
Message 3 of 4 in “mirror git repos: rsync vs. --mirror”
  1. Robin H. JohnsonMar 30, 2010
  2. Julian PhillipsMar 30, 2010
  3. Sitaram ChamartyMar 31, 2010
  4. Robin H. JohnsonMar 31, 2010

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.