From: "Shawn O. Pearce" <spearce@spearce.org>
To: deepwinter <deepwinter@winterroot.net>
Cc: git@vger.kernel.org
Subject: Re: concerns about git
Date: Mon, 13 Oct 2008 11:19:41 -0700 [thread overview]
Message-ID: <20081013181941.GT4856@spearce.org> (raw)
In-Reply-To: <19959918.post@talk.nabble.com>
deepwinter <deepwinter@winterroot.net> wrote:
>
> i've been looking into using git for some version control and it looks
> great.. except for 1 thing that really disturbs me. why is the .git
> repository stored within the working copy? this is seems like a recipe for
> accidental deletion. if you are an individual using version control lets
> say for just your own work, there is a lot of security that is gained from
> at least having your repository within a different directory, or better on a
> different partition. this ensures that accidental deletions or hard drive
> crashes are less likely to result in loosing the ENTIRE project! of course,
> accidentally deleting your working copy is stupid, but it does happen. git
> seems to offer no protection against this kind of mistake for the individual
> coder.. or is there some way to have git put the actual repository files in
> a different directory? (can't find info on that)
Because every working copy is equal. They all have a copy of the
project's metadata in the .git/ directory.
If you want a backup, create one with clone and push to it every
so often, e.g.:
# one time setup
$ git clone --bare . /some/other/drive/project.git
$ git remote add backup /some/other/drive/project.git
# then every once in a while, or from a cron job
$ git push --all backup
Of course since Git is distributed you can you use this same approach
to make backups to other systems. You can even edit the .git/config
to give the [remote "backup"] section more than one url line, so
that "git push --all backup" will send updated copies to multiple
locations at once.
Who needs a central repository like SVN or CVS when you can have 3
or 4, on just as many disks, in different buildings, and possibly
different parts of the world. Yes, I keep my real work that I care
about backed up under different providers, with their data centers
located in different countries. And of course extra copies locally,
in case the 'net is down.
--
Shawn.
next prev parent reply other threads:[~2008-10-13 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 18:12 concerns about git deepwinter
2008-10-13 18:19 ` Shawn O. Pearce [this message]
2008-10-13 18:40 ` David Tweed
2008-10-13 19:51 ` Brandon
2008-10-14 11:25 ` Ciprian Dorin Craciun
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=20081013181941.GT4856@spearce.org \
--to=spearce@spearce.org \
--cc=deepwinter@winterroot.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.