git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Sam Vilain <sam@vilain.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Temporary directories getting errantly added into trees
Date: Wed, 21 Nov 2007 23:30:59 -0800	[thread overview]
Message-ID: <20071122073059.GA28197@soma> (raw)
In-Reply-To: <4744FCD9.7020102@vilain.net>

Sam Vilain <sam@vilain.net> wrote:
> I just got through a rather nasty debugging session with git-rebase,
> which relies on a .dotest directory.  Turns out that .dotest was
> accidentally added to the tree in the history of the commit that was
> being rebased onto.

Hi Sam,

Ouch

> There are a lot of temporary files like that made by various scripts -
> eg, git-filter-branch makes .git-rewrite, etc.
> 
> I think it would be a good thing for all if you had to work very hard to
> put files like this in the tree, or perhaps it would be better to go
> through and make all the tools that create these temporary directories
> create them under .git instead.

Polluting the working tree is definitely a bad thing to do IMNSHO.

git-rebase --merge already puts its temporary directory inside
.git/.dotest-merge.  I hoped to set an example with that and
get more tools to do the same; but it hasn't happened yet...

-- 
Eric Wong

  reply	other threads:[~2007-11-22  7: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 [this message]
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
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=20071122073059.GA28197@soma \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --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).