From: david@lang.hm
To: Ramagudi Naziir <naziirr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: rsync vs. git-push/pull ? (+kudus)
Date: Sat, 6 Sep 2008 23:27:39 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0809062326000.8096@asgard.lang.hm> (raw)
In-Reply-To: <dfb262380809062311i3fffb900m5d73f5396b403dbe@mail.gmail.com>
On Sun, 7 Sep 2008, Ramagudi Naziir wrote:
> Hi all,
>
> I have several local git repositories on my machine. I'm the only
> user, and use them only locally. Now, sometimes when I need to work
> remotely, I just rsync my repositories to my laptop, and keep working
> there. When I finish (few hours, days or sometimes weeks later), I
> just rsync everything back to my local git repositories on my main
> workstation, and continue working there.
>
> Now I was wondering whether it's OK or whether there are bad
> implication I might not think of working this way. For example, maybe
> some of these little git files are named differently on each machine,
> and rsyncing them back and forth makes me piling a lot of clutter (in
> that case maybe git-gc will clean up everything). Or maybe something
> else horrid is going on and I really should just use git-push or pull.
the git files are names by their content so you don't need to worry about
them being named differently
> I really prefer rsync to git-push/pull since it is much more easier -
> It's one command that syncs my whole working folder, including the git
> repositories..
the problems you can run into with rsync all end up related to one of two
things.
1. what happens if the sync gets interrupted
2. what happens if the source gets updated during the sync
in your case these cannot happen without you knowing it, so you should be
ok.
David Lang
next prev parent reply other threads:[~2008-09-07 6:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 6:11 rsync vs. git-push/pull ? (+kudus) Ramagudi Naziir
2008-09-07 6:27 ` david [this message]
2008-09-10 6:31 ` Ramagudi Naziir
2008-09-10 13:27 ` david
2008-09-07 7:38 ` David Brown
2008-09-10 6:35 ` Ramagudi Naziir
2008-09-10 7:05 ` Matthieu Moy
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=alpine.DEB.1.10.0809062326000.8096@asgard.lang.hm \
--to=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=naziirr@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).