git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Israel Garcia <igalvarez@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: backup git repo on every commit
Date: Tue, 13 Oct 2009 11:18:13 -0700	[thread overview]
Message-ID: <20091013181813.GY9261@spearce.org> (raw)
In-Reply-To: <194a2c240910131114q19b6c822t5806d20005341cb4@mail.gmail.com>

Israel Garcia <igalvarez@gmail.com> wrote:
> BTW, is there any git-dump or git-backup command to do some kind of
> backup I'm looking for?

No, you backup git by making a clone.  E.g. `git clone --bare`.
Since this leaves you with a directory, you need to then perhaps
use some sort of file combiner tool like tar or zip to produce a
single file for backup to tape.

You can incrementally update that backup clone using git push to
write into it, or you can just blow it away and recreate it each
time you make a backup.

One could also use `git bundle` to create backup file that had
everything packaged in one neat file, but this can be slightly
harder to work with since a bundle is not a git repository.
 
-- 
Shawn.

  reply	other threads:[~2009-10-13 18:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 13:41 backup git repo on every commit Israel Garcia
2009-10-12 14:08 ` Christian Himpel
2009-10-12 14:15 ` Shawn O. Pearce
2009-10-12 14:25   ` Israel Garcia
2009-10-12 14:30     ` Shawn O. Pearce
2009-10-12 14:39       ` Israel Garcia
2009-10-13 16:43       ` Israel Garcia
2009-10-13 17:49         ` Shawn O. Pearce
2009-10-13 18:08           ` Israel Garcia
2009-10-13 18:18             ` Shawn O. Pearce
2009-10-13 18:14           ` Israel Garcia
2009-10-13 18:18             ` Shawn O. Pearce [this message]
2009-10-12 18:35   ` Christian Himpel
2009-10-12 18:37     ` Shawn O. Pearce

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=20091013181813.GY9261@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=igalvarez@gmail.com \
    /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).