From: Jonathan Nieder <jrnieder@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org, fbriere@fbriere.net, drizzd@aon.at
Subject: Re: [long] worktree setup cases
Date: Thu, 21 Oct 2010 11:01:34 -0500 [thread overview]
Message-ID: <20101021160134.GA3732@burratino> (raw)
In-Reply-To: <AANLkTikwApJ2EtJNiOZPHVrz6seJNP-zEqzH_b62ksLf@mail.gmail.com>
Nguyen Thai Ngoc Duy wrote:
> On Thu, Oct 21, 2010 at 10:30 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> Speaking of which, it is not clear to me that core.worktree should
>> fall under the forbidden case discussed above. If it does, what is
>> the point of making it configurable?
>
> I was not the one who introduced core.worktree, so I can't really
> tell. Maybe less keystrokes?
Yeah, it seems you're totally right. :(
So in clarifying the semantics, core.worktree without GIT_DIR should
be forbidden. But consider this a feature request. By the time
core.worktree has been read, it is obvious what the GIT_DIR was
supposed to be:
References:
- v0 (GIT_TOP_DIR):
http://thread.gmane.org/gmane.comp.version-control.git/38382
- v1 (GIT_WORK_DIR):
http://thread.gmane.org/gmane.comp.version-control.git/41902
- v2 (GIT_WORK_TREE):
http://thread.gmane.org/gmane.comp.version-control.git/42416
next prev parent reply other threads:[~2010-10-21 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 8:59 [long] worktree setup cases Nguyen Thai Ngoc Duy
2010-10-20 19:07 ` Jonathan Nieder
2010-10-20 19:18 ` Jonathan Nieder
2010-10-21 1:46 ` Nguyen Thai Ngoc Duy
2010-10-21 3:30 ` Jonathan Nieder
2010-10-21 12:50 ` Nguyen Thai Ngoc Duy
2010-10-21 16:01 ` Jonathan Nieder [this message]
2010-10-23 10:12 ` Nguyen Thai Ngoc Duy
2010-10-21 18:51 ` Enrico Weigelt
2010-10-22 0:34 ` Nguyen Thai Ngoc Duy
2010-10-22 5:00 ` Enrico Weigelt
2010-10-22 5:28 ` .git file (Re: [long] worktree setup cases) Jonathan Nieder
2010-10-22 5:36 ` [long] worktree setup cases Nguyen Thai Ngoc Duy
2010-10-20 21:00 ` Junio C Hamano
2010-10-21 2:23 ` Nguyen Thai Ngoc Duy
2010-10-21 19:01 ` Enrico Weigelt
2010-10-21 23:06 ` Junio C Hamano
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=20101021160134.GA3732@burratino \
--to=jrnieder@gmail.com \
--cc=drizzd@aon.at \
--cc=fbriere@fbriere.net \
--cc=git@vger.kernel.org \
--cc=pclouds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.