git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Habouzit <madcoder@madism.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: fixing workdirs
Date: Fri, 9 Jul 2010 09:56:17 +0200	[thread overview]
Message-ID: <20100709075617.GD2304@madism.org> (raw)
In-Reply-To: <7v7hl5pxt0.fsf@alter.siamese.dyndns.org>

On Thu, Jul 08, 2010 at 12:40:11PM -0700, Junio C Hamano wrote:
> Pierre Habouzit <madcoder@madism.org> writes:
> 
> > for the first one, the fix is simple: workdirs have now a name, and
> > their HEAD reflog lives in the "master" git repository reflog namespace
> > under logs/workdir/$workdir_name/HEAD. The workdir HEAD reflog is then a
> > symlink to the masters.
> 
> I think this is a sane thing to do, except for the "symlink" part but that
> would be just a minor implementation detail.

What would you suggest instead of the symlink then ? (knowing that all
the workdir is just a full symlink farm at them moment).

> > For the second one, when a workdir is created, a [workdir "foo"] section
> > is added to the master directory, with a path configuration variable
> > pointing to the ... path of the working directory.
> 
> Ok.

> > ... git checkout would check that no other workdir is currently "on
> > the same branch", and would refuse to checkout to a branch that is
> > already checkouted elsewhere.
> 
> I am personally fine with this, but if there is no way to override this
> refusal it may break some people's existing workflow.  I dunno.

Well it's probably fine to have a switch to override it of course, or
like it was suggested to prevent updating the reference instead. But
that sounds harder, and if you want to override it, it means that a lot
of commands will have to take a new argument (update-ref, commit, reset,
rebase, ...).

I'm more in favor of having checkout refusing to checkout if the
reference is already checkout-ed elsewhere, with a --ignore-workdirs or
similar switch to override this. git-checkout would still print out a
warning about the fact that /maybe/ the user is doing something crazy,
and then he'll be on his own. Plus it doesn't slow references updates
for the workdir case, only the branch switch which is way nicer.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

  parent reply	other threads:[~2010-07-09  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 11:08 fixing workdirs Pierre Habouzit
2010-07-08 18:37 ` Tait
2010-07-08 18:56   ` Joshua Jensen
2010-07-09  7:49   ` Pierre Habouzit
2010-07-08 19:40 ` Junio C Hamano
2010-07-08 19:56   ` Avery Pennarun
2010-07-09  7:56   ` Pierre Habouzit [this message]
2010-07-09 22:25     ` Junio C Hamano
2010-07-19  9:02       ` Pierre Habouzit
2010-08-17 18:34 ` Jan Hudec

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=20100709075617.GD2304@madism.org \
    --to=madcoder@madism.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).