From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [RFC PATCH] Fix gitdir detection when in subdir of gitdir
Date: Fri, 16 Jan 2009 18:23:46 +0100 [thread overview]
Message-ID: <20090116172346.GA15804@neumann> (raw)
In-Reply-To: <4970BAE5.8080006@viscovery.net>
On Fri, Jan 16, 2009 at 05:50:45PM +0100, Johannes Sixt wrote:
> Johannes Sixt schrieb:
> > Gábor's patch needs a better justification which misbehavior it tries to
> > fix, and the spot that it changes:
>
> I actually meant: "which use-case the patch tries to help". Because the
> current behavior can hardly be classified as bug. ("You have no business
> cd-ing around in .git." ;)
I agree that fiddling around in '.git' is a quite rare use case.
I did it while I was working on bash completion support for the
upcoming 'git sequencer' to see where it stores its temporary files
and what is in those files. And I got errors from the completion
script after each executed command, which quickly made me upset enough
to look after it.
I thought it worths fixing, but it's even better if it's not a bug,
because then I don't have to fix my fix (;
Regards,
Gábor
next prev parent reply other threads:[~2009-01-16 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 15:37 [RFC PATCH] Fix gitdir detection when in subdir of gitdir SZEDER Gábor
2009-01-16 16:29 ` Johannes Schindelin
2009-01-16 16:47 ` Johannes Sixt
2009-01-16 16:50 ` Johannes Sixt
2009-01-16 17:23 ` SZEDER Gábor [this message]
2009-01-16 18:07 ` Junio C Hamano
2009-01-16 20:55 ` Johannes Schindelin
2009-01-18 21:27 ` Junio C Hamano
2009-01-19 2:03 ` SZEDER Gábor
2009-01-19 3:15 ` Junio C Hamano
2009-01-19 7:17 ` Johannes Sixt
2009-01-19 2:08 ` [PATCH] t1500: extend with tests of 'git rev-parse --git-dir' SZEDER Gábor
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=20090116172346.GA15804@neumann \
--to=szeder@ira.uka.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).