All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: File "Changelog-2.6.15": missing signoffs
Date: Tue, 07 Feb 2006 17:06:05 -0800	[thread overview]
Message-ID: <43E943FD.7090508@tlinx.org> (raw)
In-Reply-To: <43E935BA.8050605@tlinx.org>

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"?

Just trying to see if I can parse large changelogs into groups
that might be easier digest and summarize...

-linda


Linda Walsh wrote:
> 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
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2006-02-08  1:06 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 ` Linda Walsh [this message]
2006-02-08 19:32   ` File "Changelog-2.6.15": missing signoffs 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=43E943FD.7090508@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 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.