From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: File "Changelog-2.6.15": unresolved commit
Date: Tue, 07 Feb 2006 16:05:14 -0800 [thread overview]
Message-ID: <43E935BA.8050605@tlinx.org> (raw)
I was examining and checking the Changelog for 2.6.15 and noticed
one commit out of the 4959 that was problematic (near line 21375):
commit 7b7abfe3dd81d659a0889f88965168f7eef8c5c6
Author: Steve French <sfrench@us.ibm.com>
Date: Wed Nov 9 15:21:09 2005 -0800
--- end of entry ---
This change has no description and no one listed as signing it off.
Was there a 1-line description for this commit and was this
commit sign off by anyone?
Do either, the missing "signoff", or "description", constitute the
possibility that the "commit" went in "unapproved" & "unaudited"?
On a less worrisome note, 62 of the 4958 commits had no "details"
beyond (after) the 1-line description. Is it safe to say that further
"details" after the 1-line description are optional?
This is the first Changelog I've examined in this detail, so I can't
say if this is a first or one-time problem.
Thanks,
-linda
next reply other threads:[~2006-02-08 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 0:05 Linda Walsh [this message]
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
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=43E935BA.8050605@tlinx.org \
--to=lkml@tlinx.org \
--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