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

Re: rsync a *bunch* of git repos

From
ATAndreas T.Auer <andreas.t.auer_gtml_37453@ursus.ath.cx>
Date
Jan 11, 2012, 08:01 UTC
Message-ID
<4F0D41E3.5020908@ursus.ath.cx>
In-Reply-To
<20120110211548.GD10255@titan.lakedaemon.net>
On 10.01.2012 22:15 Jason wrote:
Show 7 quoted lines
> The nuts and bolts of this aren't difficult, the problem is I don't have
> a complete understanding of how git stores data.  I've heard in the
> past that it uses a lot of hardlinks and softlinks.  I need to make
> sure, that once I transfer the data, and reboot the machine with the new
> partition mounted under /home, that all my git repos will be okay.
>
>

As far as I know git uses hardlinks to save diskspace, but it doesn't rely on hardlinks to work. It also works with filesystems that don't support hardlinks. But without hardlinks you will probably waste disk space so I recommend the -H parameter to rsync, which preserve hardlinks, if possible. If you have hundreds of git repos that are cloned from each other, than this should make a difference.

Previous: Jason
Message 8 of 8 in “rsync a *bunch* of git repos”
  1. JasonJan 10, 2012
  2. Seth RobertsonJan 10, 2012
  3. Philip OakleyJan 10, 2012
  4. Junio C HamanoJan 10, 2012
  5. SergioJan 11, 2012
  6. Neal KreitzingerJan 11, 2012
  7. JasonJan 24, 2012
  8. Andreas T.AuerJan 11, 2012

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.