From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, <git@vger.kernel.org>
Subject: Re: [PATCH] t/README: document --root option
Date: Sat, 12 Jun 2010 09:58:08 +0200 [thread overview]
Message-ID: <201006120958.08607.trast@student.ethz.ch> (raw)
In-Reply-To: <20100612013019.GA27604@coredump.intra.peff.net>
Jeff King wrote:
> On Fri, Jun 11, 2010 at 01:48:26PM -0700, Junio C Hamano wrote:
> >
> > Then...
> >
> > Create "trash" directories used to store all temporary data during
> > testing under <directory>, instead of the t/ directory.
>
> Yeah, that is much better, IMHO.
I see you already picked that up. Thanks!
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2010-06-12 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 18:24 [PATCH] t/README: document --root option Thomas Rast
2010-06-10 21:48 ` Jeff King
2010-06-11 20:48 ` Junio C Hamano
2010-06-12 1:30 ` Jeff King
2010-06-12 7:58 ` Thomas Rast [this message]
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=201006120958.08607.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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).