From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: linux-next: unsigned commit ...
Date: Thu, 02 Dec 2010 14:38:16 -0800 [thread overview]
Message-ID: <4CF81FD8.3080208@schaufler-ca.com> (raw)
In-Reply-To: <20101203092928.367d45c0.sfr@canb.auug.org.au>
The problem was in my converting to a git based submission
process, not with the level of review, although I can see how
the two would be indistinguishable. Thank you for the follow-up.
On 12/2/2010 2:29 PM, Stephen Rothwell wrote:
> Hi James,
>
> Commit 676dac4b1bee0469d6932f698aeb77e8489f5861 ("This patch adds a new
> security attribute to Smack called") that was added to your tree today
> has no Signed-off-by and could do with a better summary line in the
> commit message. And probably a better explanation of what it does.
>
> Makes me wonder about the level of review it received :-(
>
next prev parent reply other threads:[~2010-12-02 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 22:29 linux-next: unsigned commit Stephen Rothwell
2010-12-02 22:38 ` Casey Schaufler [this message]
2010-12-03 1:21 ` James Morris
2010-12-03 4:46 ` Stephen Rothwell
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=4CF81FD8.3080208@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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