All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <sgarman@zenlinux.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] tar: Upgrade to v1.23
Date: Tue, 03 Aug 2010 08:07:04 -0700	[thread overview]
Message-ID: <4C583098.5050007@zenlinux.com> (raw)
In-Reply-To: <AANLkTimKyWgQyN0T6VExcAjE0=M2kuCLvbq-hEYJ70Fc@mail.gmail.com>

On 08/02/2010 11:14 PM, Frans Meulenbroeks wrote:
> 2010/8/3 Scott Garman<sgarman@zenlinux.com>
>
>> From: Scott Garman<scott.a.garman@intel.com>
>>
>> * Addresses CVE-2010-0624
>>
>
> Please have a look at http://wiki.openembedded.net/index.php/Commit_Policy
>
> And especially this section:

Hi Frans,

Thanks for sending me these pointers. However, I'm a bit unclear on what 
needs improvement. The subject line of this patch email corresponds to 
the first line of the commit message, doesn't it?

To go case-by-case:

>   * Have a clear commit message (example
> <http://wiki.openembedded.net/index.php/Commit_log_example>):
>      - The first line of commit is a summary of the changes.

Which in this case is:

tar: Upgrade to v1.23

>      - The first line should start with the name of the recipe the
> change affects.

tar: <- that's the name of the recipe

>      - The rest of the message should give more details on the change
> as appropriate.

Given how trivial the change is, there's not much else to say. I did 
make mention of the security advisory the upgrade fixes:

* Addresses CVE-2010-0624

>      - Mention the affected bug numbers if appropriate.

N/A

>      - Give credit where credit is due. If you commit someone else's
> work more or
>        less verbatim, you should use *git commit --author
> $mail-of-author*. If pulling
>        changes from somewhere like Poky or OpenMoko there is no problem with that
>        but mention where the changes came from.

Again, with something this trivial, I doubt anyone would consider me 
taking credit for something inappropriately.

>      - Include a Signed-off-by: line indicating the change has valid certificate
>        of origin as per the Linux kernel<http://lwn.net/Articles/139916/>

and indeed, I ended my commit with:

Signed-off-by: Scott Garman <sgarman@zenlinux.com>

I'm happy to respin the patch if needed, but I'm still unsure what needs 
to be changed.

Thanks,

Scott

-- 
Scott Garman
sgarman at zenlinux dot com



  reply	other threads:[~2010-08-03 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  4:01 [PATCH] tar: Upgrade to v1.23 Scott Garman
2010-08-03  4:13 ` Scott Garman
2010-08-03  6:14 ` Frans Meulenbroeks
2010-08-03 15:07   ` Scott Garman [this message]
2010-08-03 16:07     ` Frans Meulenbroeks
2010-08-03 21:07       ` Scott Garman

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=4C583098.5050007@zenlinux.com \
    --to=sgarman@zenlinux.com \
    --cc=openembedded-devel@lists.openembedded.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.