From: Jeff King <peff@peff.net>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
git@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH/RFC] fsck: complain when .gitignore and .gitattributes are symlinks
Date: Tue, 22 Jan 2019 02:23:59 -0500 [thread overview]
Message-ID: <20190122072359.GE28555@sigill.intra.peff.net> (raw)
In-Reply-To: <a0aef5a7-eb69-8dd8-abb7-4db6d1de4a26@ramsayjones.plus.com>
On Fri, Jan 18, 2019 at 01:41:08AM +0000, Ramsay Jones wrote:
> I don't do this "from time to time", but *every* build on all
> platforms! :-D
>
> As I have mentioned before, I run the script on 'master', 'next'
> and 'pu', but I don't look at the results for 'master', I simply
> look at the diffs master->next and next->pu.
Ah, ok, that explains it, then. As you noted, these made it straight to
master because of the security embargo.
Thanks for satisfying my curiosity (and for running your script!).
I do wonder if you might be better off comparing master@{1} to master to
see if anything new appears (since I assume the whole point is ignoring
historical false positives, and just looking at patches under active
development).
-Peff
next prev parent reply other threads:[~2019-01-22 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 23:09 [PATCH/RFC] fsck: complain when .gitignore and .gitattributes are symlinks Jonathan Nieder
2019-01-17 17:00 ` Jeff King
2019-01-17 20:13 ` Junio C Hamano
2019-01-17 21:24 ` Jeff King
2019-01-18 1:41 ` Ramsay Jones
2019-01-22 7:23 ` Jeff King [this message]
2019-01-22 18:19 ` Ramsay Jones
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=20190122072359.GE28555@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=ramsay@ramsayjones.plus.com \
--cc=torvalds@linux-foundation.org \
/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).