git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Martin Langhoff <martin.langhoff@gmail.com>
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:30:40 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711221129170.27959@racer.site> (raw)
In-Reply-To: <46a038f90711220301o1cbb16b7g79eea541f8ca5e58@mail.gmail.com>

Hi,

On Fri, 23 Nov 2007, Martin Langhoff wrote:

> On Nov 22, 2007 11:55 PM, Johannes Schindelin
> 
> > ... 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.
> 
> when it comes to .dotest/patch, it must be reasonably accessible. When 
> git-am refuses to apply a patch, and I am resolving things by hand, I 
> need it pretty handy. I also sometimes edit .dotest/msg-clean.

Maybe install a .dotest/ symlink for a few "git eons", i.e. some 6 months?

Although this will not work on Windows, I see not much problems in it, 
since Windows users are not big in scripting (at least the git 
type) anyway.

Ciao,
Dscho

  reply	other threads:[~2007-11-22 11:31 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 [this message]
2007-11-22 11:37     ` Junio C Hamano
2007-11-22 11:16   ` Jeff King
2007-11-22 11:32     ` Johannes Schindelin
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.0711221129170.27959@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    --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).