From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Sam Vilain <sam@vilain.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Temporary directories getting errantly added into trees
Date: Thu, 22 Nov 2007 11:32:55 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711221130510.27959@racer.site> (raw)
In-Reply-To: <20071122111600.GF10389@sigill.intra.peff.net>
Hi.
On Thu, 22 Nov 2007, Jeff King wrote:
> On Thu, Nov 22, 2007 at 10:55:00AM +0000, Johannes Schindelin wrote:
>
> > Yes, I know, existing tools could rely on the location. But then, I
> > do not think that tools should be allowed to be _that_ married to
> > particular implementations. And indeed, I see no reason why a tool
> > should access .dotest, except for accessing .dotest/patch, and then it
> > will be very obvious where it fails.
>
> Another reason might be something like:
>
> test -d .dotest && die "rebase or am already in progress"
>
> which some of the git tools do, and which third party scripts might care
> about.
Yep, for example this nice bash-completion addendum which changes the
prompt according to the current repository's state.
I hope that a symlink .dotest -> .git/rebase (as I suggested in a reply to
Martin) would help that, but in the long run I'd appreciate losing even
that.
Ciao,
Dscho
P.S.: note that even a symlink would already help the situation described
by Sam.
next prev parent reply other threads:[~2007-11-22 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 3:51 Temporary directories getting errantly added into trees Sam Vilain
2007-11-22 7:30 ` Eric Wong
2007-11-22 10:43 ` Jeff King
2007-11-22 10:55 ` Johannes Schindelin
2007-11-22 11:01 ` Martin Langhoff
2007-11-22 11:30 ` Johannes Schindelin
2007-11-22 11:37 ` Junio C Hamano
2007-11-22 11:16 ` Jeff King
2007-11-22 11:32 ` Johannes Schindelin [this message]
2007-11-23 8:21 ` Karl Hasselström
2007-11-24 0:07 ` Sam Vilain
2007-11-23 14:44 ` Marco Costalba
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.0711221130510.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sam@vilain.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).