From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j6t@kdbg.org>, git@vger.kernel.org
Subject: Re: [PATCH] tests: add some script lint checks
Date: Mon, 12 Apr 2010 00:41:45 -0700 [thread overview]
Message-ID: <7vochpm81y.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100412065234.GA12462@coredump.intra.peff.net> (Jeff King's message of "Mon\, 12 Apr 2010 02\:52\:34 -0400")
Jeff King <peff@peff.net> writes:
> As maintainer, Junio, you might want to run at
> least with TEST_LINT = test-lint-duplicate, since you can then catch
> duplicates introduced by merges and fix them up as part of the merge.
Thanks. They are caught by pre-applypatch from 'todo' these days. I
should also perhaps check for the executable bit there.
prev parent reply other threads:[~2010-04-12 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 6:52 [PATCH] tests: add some script lint checks Jeff King
2010-04-12 7:41 ` Junio C Hamano [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=7vochpm81y.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--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).