From: Miles Bader <miles@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] init, clone: support --real-git-dir for .git file
Date: Fri, 04 Mar 2011 13:13:32 +0900 [thread overview]
Message-ID: <buozkpb8qvn.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <7v8vwv927a.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
>> Instead of creating the repository at $GIT_DIR, --real-git-dir will
>> tell git to put the repository there, then make $GIT_DIR a .git file
>> that points to --real-git-dir.
>
> Just like you, I am also bad at naming things, so I cannot offhand suggest
> a better name, even though I _know_ --real-git-dir sounds horrible.
--separate-git-dir ?
[Terms like "separate source dir" and "separate build dir" seems to be
common when talking about build systems, and it seems a somewhat
similar situation -- separation of usually co-located information.]
-miles
--
It wasn't the Exxon Valdez captain's driving that caused the Alaskan oil spill.
It was yours. [Greenpeace advertisement, New York Times, 25 February 1990]
next prev parent reply other threads:[~2011-03-04 4:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 12:43 [PATCH/RFC] init, clone: support --real-git-dir for .git file Nguyễn Thái Ngọc Duy
2011-03-03 21:13 ` Piotr Krukowiecki
2011-03-03 23:31 ` Junio C Hamano
2011-03-04 7:41 ` Piotr Krukowiecki
2011-03-04 12:26 ` Nguyen Thai Ngoc Duy
2011-03-04 18:09 ` Piotr Krukowiecki
2011-03-04 18:41 ` Junio C Hamano
2011-03-04 4:19 ` Nguyen Thai Ngoc Duy
2011-03-04 0:08 ` Junio C Hamano
2011-03-04 4:13 ` Miles Bader [this message]
2011-03-04 4:33 ` Nguyen Thai Ngoc Duy
2011-03-04 4:23 ` Nguyen Thai Ngoc Duy
2011-03-04 6:00 ` Junio C Hamano
2011-03-04 6:39 ` Nguyen Thai Ngoc Duy
2011-03-04 6:57 ` Miles Bader
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=buozkpb8qvn.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.