From: Jeff King <peff@peff.net>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] t/helper: ignore only executable files
Date: Mon, 23 Sep 2019 18:31:46 -0400 [thread overview]
Message-ID: <20190923223145.GB22645@sigill.intra.peff.net> (raw)
In-Reply-To: <20190920093609.24935-1-szeder.dev@gmail.com>
On Fri, Sep 20, 2019 at 11:36:09AM +0200, SZEDER Gábor wrote:
> Ignoring everything but sources has the drawback that building an
> older version of Git (e.g. during bisecting) creates all those
> executables, and after going back to e.g. current 'master' the usual
> cleanup commands like 'make clean' or 'git clean -fd' don't remove
> them (the former doesn't know about them, and the latter doesn't
> remove ignored files).
Good reasoning. I've definitely been bit by this before when manually
testing something (for some reason, I still haven't trained my fingers
to type "test-tool foo" instead of "test-foo").
A similar one that bites me sometimes is that modern t5801 will fail
with an old built version of git-remote-testgit. That one _is_ correctly
handled in .gitignore, but you do have to remember to run "git clean".
But that's the best we can do, I think, unless we want to make t5801
more paranoid about running the version from t/t5801/git-remote-testgit.
> So let's ignore only the executable files under 't/helper/, i.e.
> 'test-tool' and the three other remaining executables that could not
> be integrated into 'test-tool' (no need to ignore object files, as
> they are already ignored by our toplevel '.gitignore').
Sounds like the right solution, and the patch looks good to me.
-Peff
prev parent reply other threads:[~2019-09-23 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 9:36 [PATCH] t/helper: ignore only executable files SZEDER Gábor
2019-09-23 22:31 ` Jeff King [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=20190923223145.GB22645@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.com \
/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).