From: "Ramagudi Naziir" <naziirr@gmail.com>
To: "David Brown" <git@davidb.org>
Cc: git@vger.kernel.org
Subject: Re: rsync vs. git-push/pull ? (+kudus)
Date: Wed, 10 Sep 2008 09:35:44 +0300 [thread overview]
Message-ID: <dfb262380809092335q3d61488gf680c91ac23e69da@mail.gmail.com> (raw)
In-Reply-To: <20080907073821.GA28289@linode.davidb.org>
Hi David,
On Sun, Sep 7, 2008 at 10:38 AM, David Brown <git@davidb.org> wrote:
> On Sun, Sep 07, 2008 at 09:11:47AM +0300, Ramagudi Naziir wrote:
>
>> 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..
>
> I used to do this quite a bit until after a few times I forgot to sync
> before changing things. I solved this by creating a bare repo I could
> push/pull from, and pushing one of them to it, then fetching and
> merging in the other.
can you please elaborate on this technique ? I don't really get it.
You mean you have an empty git repository somewhere, with which you
are synchronizing all other repositories ?
>
> After getting more familiar with git, I now use git with push/pull for
> pretty much anything I want synchronized. It nicely keeps track of
> what I've done, whereas it is easier with rsync, or even unison, to
> forget to do the sync.
so you have myriad of git repositories ? and you push/pull all of them
every time you move to another station ? I also have a lot of git
repositories, even for stuff other than source code projects.
thank you
naziir
>
> David
>
next prev parent reply other threads:[~2008-09-10 6:37 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
2008-09-10 13:27 ` david
2008-09-07 7:38 ` David Brown
2008-09-10 6:35 ` Ramagudi Naziir [this message]
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=dfb262380809092335q3d61488gf680c91ac23e69da@mail.gmail.com \
--to=naziirr@gmail.com \
--cc=git@davidb.org \
--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).