From: Willy Tarreau <w@1wt.eu>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Julian Phillips <julian@quantumfyre.co.uk>, git@vger.kernel.org
Subject: Re: Multiple working trees with GIT ?
Date: Thu, 24 Jan 2008 13:56:06 +0100 [thread overview]
Message-ID: <20080124125606.GB13247@1wt.eu> (raw)
In-Reply-To: <alpine.LSU.1.00.0801241102260.5731@racer.site>
On Thu, Jan 24, 2008 at 11:04:42AM +0000, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 24 Jan 2008, Julian Phillips wrote:
>
> > You might want to have a look at the git-new-workdir script in contrib,
> > it does basically the same thing. It's been there for about 10 months
> > now. It was based on an email from Junio:
> >
> > http://article.gmane.org/gmane.comp.version-control.git/41513/
>
> FWIW I have a patch to do something like that in "git branch" itself.
>
> > However, there are some caveats about using this approach, basically
> > about the fact that there is nothing stopping you from updating refs
> > that are currently checked out in another directory and causing yourself
> > all sorts of pain ... the topic has cropped up a couple of times on the
> > list since the script was added.
>
> I agree; maybe we should have a telltale file
> "refs/heads/<bla>.checkedout" which is heeded by "git checkout" and "git
> branch -d/-D", as well as update_ref() (should only update that ref when
> it HEAD points to it)?
Why not generalize this into HEAD.$branch (thus limiting to one checkout
per branch) or HEAD.$checkoutdir ?
Best regards,
Willy
next prev parent reply other threads:[~2008-01-24 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 7:49 Multiple working trees with GIT ? Willy Tarreau
2008-01-24 9:59 ` Julian Phillips
2008-01-24 11:04 ` Johannes Schindelin
2008-01-24 12:56 ` Willy Tarreau [this message]
2008-01-24 13:38 ` Johannes Schindelin
2008-01-24 14:10 ` Willy Tarreau
2008-01-24 12:59 ` Willy Tarreau
2008-01-24 14:51 ` J. Bruce Fields
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=20080124125606.GB13247@1wt.eu \
--to=w@1wt.eu \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
/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).