From: Noah Silverman <noah@smartmediacorp.com>
To: git@vger.kernel.org
Subject: Advice on choosing git
Date: Tue, 11 May 2010 23:31:34 -0700 [thread overview]
Message-ID: <4BEA4B46.6010009@smartmediacorp.com> (raw)
Hi,
I'm looking for both a version control system and backup system.
Up for consideration are Git, Bazaar, and generic Rsync.
In the past, I've just use Rsync to sync up the directories I care
about. I just sync all the machines with the remote server. Often,
I'll start working on a file or two at the office, rsync my work to the
server, then rsync them back down to my home machine to keep working at
night. This works, but doesn't give me any nice VCS features, history,
collaboration, etc. So clearly it is time to upgrade the system.
I work on both a laptop, and office machine and a home machine.
1) I'd like to keep my documents directory synced between the office and
home machines.
2) I'd like to keep two or three sub directories of this synced with my
laptop
3) We have a server in "the cloud" where I like to keep backups of my
documents. Just in case.
3) I have a few project where I am the only developer, but want a VCS to
manage my changes.
4) I have 3-4 projects where there are a team of 3 of us and I want to
use a VCS.
In general, I might work on a given project/file on any of my machines
in a given day. Not everything is a full "branch", but just some
ongoing work. I've always followed the practice of backup up any
changed files remotely, just in case. So with a VCS, I don't want a new
version number for everytime I change a file. As I do incremental work
across three machines, it could quickly turn versioning nightmare.
I guess, that I need just keep some files backed up (and/or synced) as
they're not "working projects". I will add new documents and
occasionally edit others, but no real need for versioning. Other files
are working projects (possible with collaboration) and need active VCS.
I've heard amazing things about Git, but have a few concerns. Hopefully
someone here can offer some suggestions.
1) Size. THIS IS MY MAIN CONCERN - If I want to sync my home, office,
and server Document directories. From what I have read, I will
effectively have multiple copies of each item on my hard drive, thus
eating up a lot of space (One of the "working file"and several in the
.git directory.) If I have multiple changes to a file, then I have
several full versions of it on my machine. This could be a problem for
a directory with 100GB or more, especially on a laptop with limited hard
drive space. I know Subversion is a dirty word around here, but it
seemed to only annotate and send the changes
2) Sub-directory selection. On my laptop, I only want a few
sub-directories to be synced up. I don't need my whole document tree,
but just a few directories of things I work on.
Bazaar also looks like a possible option, but I'm not sure it handles
drive usage better. Their website has a lengthy manifesto about how
they're better than Git, but I don't have enough experience with either
to make an informed decision.
Any and all suggestions are welcome and appreciated.
Thank You,
--
Noah
next reply other threads:[~2010-05-12 6:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 6:31 Noah Silverman [this message]
2010-05-12 9:04 ` Advice on choosing git Dmitry Potapov
2010-05-12 9:15 ` Ramkumar Ramachandra
2010-05-12 9:24 ` Jonathan Nieder
2010-05-13 0:18 ` Joe Brenner
2010-05-13 0:31 ` Avery Pennarun
2010-05-13 11:48 ` Matthieu Moy
2010-05-13 17:31 ` Avery Pennarun
2010-05-19 0:37 ` Anthony W. Youngman
2010-05-19 1:12 ` Avery Pennarun
2010-05-13 11:42 ` Matthieu Moy
2010-05-13 11:51 ` Jeff King
2010-05-13 18:20 ` Martin Langhoff
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=4BEA4B46.6010009@smartmediacorp.com \
--to=noah@smartmediacorp.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).