From: Heikki Orsila <shdl@zakalwe.fi>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: bill lam <cbill.lam@gmail.com>, git@vger.kernel.org
Subject: Re: how to backup git
Date: Mon, 12 May 2008 21:07:20 +0300 [thread overview]
Message-ID: <20080512180720.GN31039@zakalwe.fi> (raw)
In-Reply-To: <alpine.DEB.1.00.0805121804500.30431@racer>
On Mon, May 12, 2008 at 06:07:28PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 12 May 2008, Heikki Orsila wrote:
>
> > On Mon, May 12, 2008 at 04:08:21PM +0100, Johannes Schindelin wrote:
> > > No, rsync is particularly dumb in that respect. The safest thing
> > > would be to back up the reflogs first (e.g. with rsync), then repack
> > > and then clone (the clone will transmit the objects referenced by the
> > > reflogs, too). Note: the same holds _not_ true for a simple fetch.
> > >
> > > But then, you usually do not want to back up reflogs anyway, since
> > > they are purely local and not visible to anybody else.
> >
> > Is there a simple and efficient mechanism for incremental backups?
>
> Umm. "git fetch"?
>
> Like I said, it does not get the reflogs, but if you want to back up a
> repository, the safest is to clone once, and fetch later. Or you could
> set up a remote with the --mirror option, if you want to preserve the
> refs' namespaces.
Preferably some solution that does not require too much understanding of
Git internals so that admins will actually use it, instead of hacking
their own inefficient backup scripts.
Could someone please write a "git-backup" script?-)
--
Heikki Orsila
heikki.orsila@iki.fi
http://www.iki.fi/shd
next prev parent reply other threads:[~2008-05-12 18:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 6:08 how to backup git bill lam
2008-05-12 6:36 ` Tobias Sarnowski
2008-05-12 6:40 ` Sverre Hvammen Johansen
2008-05-12 13:11 ` Eric Hanchrow
2008-05-12 13:28 ` Johannes Schindelin
2008-05-12 14:13 ` bill lam
2008-05-12 14:54 ` Miklos Vajna
2008-05-12 15:08 ` Johannes Schindelin
2008-05-12 15:27 ` Heikki Orsila
2008-05-12 17:07 ` Johannes Schindelin
2008-05-12 18:07 ` Heikki Orsila [this message]
2008-05-12 18:21 ` Johannes Schindelin
2008-05-12 18:36 ` Heikki Orsila
2008-05-12 18:38 ` Heikki Orsila
2008-05-12 18:58 ` Tim Harper
2008-05-12 19:10 ` Heikki Orsila
2008-05-12 19:49 ` Sverre Rabbelier
2008-05-12 18:54 ` Jakub Narebski
2008-05-12 21:19 ` Daniel Barkalow
2008-05-12 22:26 ` Junio C Hamano
2008-05-12 23:43 ` Daniel Barkalow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080512180720.GN31039@zakalwe.fi \
--to=shdl@zakalwe.fi \
--cc=Johannes.Schindelin@gmx.de \
--cc=cbill.lam@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).