From: Roland Dreier <rdreier@cisco.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: update checkpatch.pl to version 0.19
Date: Mon, 09 Jun 2008 08:56:19 -0700 [thread overview]
Message-ID: <ada3anma9gc.fsf@cisco.com> (raw)
In-Reply-To: <20080609083301.GA6701@shadowen.org> (Andy Whitcroft's message of "Mon, 9 Jun 2008 09:33:01 +0100")
> The issue I have is I have a comprehensive test suite which is kept in
> lock step with checkpatch itself, all in my own tree. Now that is just
> noise for mainline. What I want to be able to do is keep that in lock
> step with developments in my tree, but not merge it upstream. So far
> I've not found a workable solution with git for that.
>From my naive point of view: why wouldn't we want a test suite upstream,
if one is already written?
- R.
prev parent reply other threads:[~2008-06-09 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806061922.m56JMJuq025990@hera.kernel.org>
2008-06-06 23:30 ` update checkpatch.pl to version 0.19 Greg KH
2008-06-07 6:02 ` Andrew Morton
2008-06-07 17:34 ` Greg KH
2008-06-09 8:33 ` Andy Whitcroft
2008-06-09 11:09 ` David Woodhouse
2008-06-09 22:58 ` Greg KH
2008-06-11 8:49 ` Andy Whitcroft
2008-06-09 15:56 ` Roland Dreier [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=ada3anma9gc.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.