From: Kurt Wall <kwall@kurtwerks.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: "Changelog-2.6.15": missing signoffs, descriptions
Date: Wed, 8 Feb 2006 19:10:48 -0500 [thread overview]
Message-ID: <20060209001048.GA6279@kurtwerks.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0602081457500.1564@shark.he.net>
On Wed, Feb 08, 2006 at 03:00:01PM -0800, Randy.Dunlap took 50 lines to write:
> On Wed, 8 Feb 2006, Linda Walsh wrote:
>
> > Luck, Tony wrote:
> > > On Tue, Feb 07, 2006 at 05:06:05PM -0800, Linda Walsh wrote:
> > >
> > >> Actually, ("talking" to myself?), parsing this file a bit more,
> > >> I find many (~134) that are missing "Sign-offs".
> > >>
> > >> I take it that "Sign-off"s are also "optional" on commits
> > >> and represent that the author specified under the "commit"
> > >> tag did not need a "Sign-off"?
[...]
> Linda, did you have some other point that you are trying to get to,
> or is that it? There are real efforts being made, although not
> perfect. That happens when people are involved.
> Anyway, it feels like you are just getting to the surface/edge
> of your complaint.
The way I read this thread, I thought the complaint was that she's
having difficulty writing one or more tools to process the changes
automatically. Perhaps I'm not seeing past the surface.
Kurt
--
On a paper submitted by a physicist colleague:
"This isn't right. This isn't even wrong."
-- Wolfgang Pauli
next prev parent reply other threads:[~2006-02-09 0:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 0:05 File "Changelog-2.6.15": unresolved commit Linda Walsh
2006-02-08 1:06 ` File "Changelog-2.6.15": missing signoffs Linda Walsh
2006-02-08 19:32 ` Luck, Tony
2006-02-08 22:53 ` "Changelog-2.6.15": missing signoffs, descriptions Linda Walsh
2006-02-08 23:00 ` Randy.Dunlap
2006-02-09 0:10 ` Kurt Wall [this message]
2006-02-09 0:13 ` Randy.Dunlap
2006-02-09 1:26 ` Commit validation/assurance; change control Linda Walsh
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=20060209001048.GA6279@kurtwerks.com \
--to=kwall@kurtwerks.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox