From: Junio C Hamano <gitster@pobox•com>
To: Thomas Rast <trast@inf•ethz.ch>
Cc: Thomas Rast <trast@student•ethz.ch>, <git@vger•kernel.org>
Subject: Re: [PATCH 3/4] t5510: ensure we stay in the toplevel test dir
Date: Thu, 01 Mar 2012 14:32:46 -0800 [thread overview]
Message-ID: <7vaa40kl4h.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <871upcht2h.fsf@thomas.inf.ethz.ch> (Thomas Rast's message of "Thu, 1 Mar 2012 23:09:26 +0100")
Thomas Rast <trast@inf•ethz.ch> writes:
> Junio C Hamano <gitster@pobox•com> writes:
>
>> Thomas Rast <trast@student•ethz.ch> writes:
>>
>>> The last test descended into a subdir without ever re-emerging, which
>>> is not so nice to the next test writer.
>>
>> True. Making the test suite more robust like this patch does is very much
>> appreciated.
>>
>> Is there a reason why we shouldn't be sticking to the more usual
>>
>> mkdir dups &&
>> (
>> cd dups &&
>> do whatever in dups
>> )
>>
>> pattern?
>
> None in particular. It would also perhaps reduce the churn since (as it
> touches every line anyway) it could be squashed with 2/4. Should I reroll?
No. I was just curious.
next prev parent reply other threads:[~2012-03-01 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 21:40 [PATCH 0/4] Another bundle fix: reading freed memory Thomas Rast
2012-03-01 21:40 ` [PATCH 1/4] t5510: refactor bundle->pack conversion Thomas Rast
2012-03-01 21:40 ` [PATCH 2/4] t5510: fix indent with spaces Thomas Rast
2012-03-01 21:40 ` [PATCH 3/4] t5510: ensure we stay in the toplevel test dir Thomas Rast
2012-03-01 21:57 ` Junio C Hamano
2012-03-01 22:09 ` Thomas Rast
2012-03-01 22:32 ` Junio C Hamano [this message]
2012-03-01 22:33 ` Junio C Hamano
2012-03-01 21:40 ` [PATCH 4/4] bundle: keep around names passed to add_pending_object() Thomas Rast
2012-03-01 22:05 ` Junio C Hamano
2012-03-01 22:22 ` Thomas Rast
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=7vaa40kl4h.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=trast@inf$(echo .)ethz.ch \
--cc=trast@student$(echo .)ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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