From: Alex Riesen <raa.lkml@gmail.com>
Date: Wed, 25 Nov 2009 10:08:46 GMT
Subject: Re: Git repository mesh?
Message-ID: <81b0412b0911250208v67a16637s72551a892af4b0d8@mail.gmail.com>
In-Reply-To: <fcaeb9bf0911242007t1294bddej87b48691ea283e21@mail.gmail.com>

On Wed, Nov 25, 2009 at 05:07, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> I work on a few machines so I have repositories on all of them. One
> repository can pull from or push to any other repositories (in case of
> push, it pushes on remote branches). I avoid a central repository
> because it's quite inconvenient when you just need to push some
> changes to a machine, you have to push it to the central repository
> then pull from that (and if the central repository is on WAN, double
> inconvenient). Maybe this model is just plain wrong, but it'd be fun
> to see if Git can work with this model.

You can always use fetch (and pull) without specifying a remote:

  $ git fetch host:/path/repo some-branch
  $ git log ..FETCH_HEAD # git merge FETCH_HEAD

Maybe fetch should be extended to record this operation in .git/config?

  $ git fetch ---save=host-some host:/path/repo some-branch some-branch
  $ git remote -v
  ...
  host-some	host:/path/repo (fetch)
  $