git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Domenico Andreoli <cavokz@gmail.com>, git@vger.kernel.org
Subject: Re: multiple checked out branches
Date: Wed, 1 Aug 2007 23:39:47 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708012338250.14781@racer.site> (raw)
In-Reply-To: <20070801223430.GC2911@steel.home>

Hi,

On Thu, 2 Aug 2007, Alex Riesen wrote:

> Domenico Andreoli, Thu, Aug 02, 2007 00:04:35 +0200:
> > 
> >   I would like to contemporaneously work with multiple branches out of
> > the same git repository. This does not work out of the box.
> > 
> > So I prepare multiple copies of the same repository, every one will have
> > its own checked out branch but I want to share most of their .git subdir.
> > 
> > I surely want to share the object db, the local and remote refs.
> > This way it is enough to make a round of fetches/merges/pushes to have
> > all the shared-repositories up to date.
> > 
> > I expect to do the trick with some symlinks but I am not an expert of
> > git internals. Which traps are waiting me? Any hint? Thank you.
> > 
> 
> No traps. Supported. See for "git clone -s" and "git clone -l"

That is not completely what is wanted, AFAIU:  "git clone -s" and "git 
clone -l" allow for unsynchronised branches.  For example, when you 
committed to branch "foo" in the cloned repo, branch "foo" in the original 
repo will be older until you push.

Ciao,
Dscho

      reply	other threads:[~2007-08-01 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 22:04 multiple checked out branches Domenico Andreoli
2007-08-01 22:19 ` Julian Phillips
2007-08-02  0:02   ` Domenico Andreoli
2007-08-02 17:16     ` Guilhem Bonnefille
2007-08-01 22:34 ` Alex Riesen
2007-08-01 22:39   ` Johannes Schindelin [this message]

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=Pine.LNX.4.64.0708012338250.14781@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=cavokz@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@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).