From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>,
"Mark Levedahl" <mlevedahl@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] Fix install-doc-quick target
Date: Sun, 5 Aug 2007 19:10:24 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708051909300.14781@racer.site> (raw)
In-Reply-To: <7vzm15eukf.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sun, 5 Aug 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > I do not like the behaviour "be stupid and assume cwd to be the working
> > tree root, if GIT_DIR is set and GIT_WORK_TREE is not".
> >
> > It bears _all_ kind of stupid connotations. Just imagine what would
> > happen with "git --git-dir=. add .".
> >
> > IMHO the new behaviour is _better_, since you can not shoot yourself in
> > the foot so easily. Being able to safeguard against doing a work tree
> > operation inside the git directory is a direct and elegant consequence of
> > defaulting to $GIT_DIR/.. in case $GIT_DIR ends in "/.git", and no work
> > tree if $GIT_DIR does _not_ end in "/.git".
> >
> > The semantics "if GIT_DIR is set, just assume the cwd to be the work tree
> > root unilaterally" is _broken_ as far as I am concerned.
>
> I am not disputing that. I was just pointing out that this is a
> change in semantics and we need to advertise it as such, and
> more importantly, advise people how to adjust to the new (and
> improved) world order.
Thanks. I will prepare a patch to ReleaseNotes, but that'll have to wait
until tomorrow. I'm pretty exhausted after the last night of msysGit
hacking.
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-05 18:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 15:07 rc4 - make quick-install-doc is broken Mark Levedahl
2007-08-04 15:38 ` Johannes Schindelin
2007-08-04 16:00 ` Mark Levedahl
2007-08-04 16:04 ` Johannes Schindelin
2007-08-04 16:14 ` Mark Levedahl
2007-08-04 16:21 ` Johannes Schindelin
2007-08-04 17:56 ` Mark Levedahl
2007-08-04 21:32 ` [PATCH] Fix quick-install-doc Johannes Schindelin
2007-08-04 22:09 ` René Scharfe
2007-08-05 7:07 ` [PATCH] Fix install-doc-quick target Junio C Hamano
2007-08-05 13:12 ` Johannes Schindelin
2007-08-05 17:54 ` Junio C Hamano
2007-08-05 18:10 ` Johannes Schindelin [this message]
2007-08-05 14:44 ` Johannes Schindelin
2007-08-06 22:43 ` [PATCH] (Really) " Mark Levedahl
2007-08-06 22:50 ` Johannes Schindelin
2007-08-06 23:07 ` Junio C Hamano
2007-08-06 23:38 ` Mark Levedahl
2007-08-06 23:43 ` Johannes Schindelin
2007-08-06 23:49 ` Mark Levedahl
2007-08-07 1:28 ` Junio C Hamano
2007-08-07 1:55 ` Mark Levedahl
2007-08-07 3:53 ` Junio C Hamano
2007-08-07 13:55 ` René Scharfe
2007-08-07 14:08 ` Johannes Schindelin
2007-08-04 16:08 ` rc4 - make quick-install-doc is broken Mark Levedahl
2007-08-04 16:16 ` Johannes Schindelin
2007-08-04 16:27 ` Mark Levedahl
2007-08-04 20:19 ` René Scharfe
2007-08-04 20:21 ` Johannes Schindelin
2007-08-04 20:45 ` Mark Levedahl
2007-08-04 21:33 ` Johannes Schindelin
2007-08-04 22:09 ` René Scharfe
2007-08-04 22:25 ` Johannes Schindelin
2007-08-04 22:37 ` Johannes Schindelin
2007-08-04 23:03 ` René Scharfe
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.0708051909300.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mlevedahl@gmail.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).