On Fri, 17 Aug 2012 14:47:07 +0100 Adam Prescott <[email protected]> wrote:
> > Quite probably. The problem with `git clone` is that it's supposed > > to create a repository, but we keep the mirror repositories around > > (I mean, they are not tarred and gzipped, and just sit there waiting > > for the next backup round or for being used for disaster recovery). > If you create your repository with `clone --mirror`, a simple `fetch` > should be all you need to keep a backup, unless I'm missing something. Good idea indeed. But I still prefer my approach as the full information about how to update a mirror repo is contained in the backup script itself. Each mirror repo thus has almost no identity (besides the fact it mirrors a specific repo), which, I think, is a good thing. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
