From: "Ramagudi Naziir" <naziirr@gmail.com>
To: david@lang.hm
Cc: git@vger.kernel.org
Subject: Re: rsync vs. git-push/pull ? (+kudus)
Date: Wed, 10 Sep 2008 09:31:29 +0300 [thread overview]
Message-ID: <dfb262380809092331i3399731cqdec3b2bb79d2fcdd@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0809062326000.8096@asgard.lang.hm>
Hi David,
On Sun, Sep 7, 2008 at 9:27 AM, <david@lang.hm> wrote:
> 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
But can I end up having a lot of clutter ? e.g. if these files change,
then rsync will copy the new files, and the old ones will still be
kept, piling up like crud. is this correct ? is it problematic ? will
git-gc fix it ?
next prev parent reply other threads:[~2008-09-10 6:32 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
2008-09-10 6:31 ` Ramagudi Naziir [this message]
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=dfb262380809092331i3399731cqdec3b2bb79d2fcdd@mail.gmail.com \
--to=naziirr@gmail.com \
--cc=david@lang.hm \
--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).