From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] lib/bb/siggen.py: ensure dumped signatures have group R/W
Date: Sun, 13 May 2012 20:02:51 +0100 [thread overview]
Message-ID: <1336935771.2711.22.camel@ted> (raw)
In-Reply-To: <1336785711-13353-1-git-send-email-josh@linux.intel.com>
On Fri, 2012-05-11 at 18:21 -0700, Joshua Lock wrote:
> We anticipate signatures being shared amongst peers in a group so ensure
> they have rw-rw-r-- permissions to facilitate this.
>
> Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> lib/bb/siggen.py | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
Merged to master (along with 1/2) thanks.
Richard
prev parent reply other threads:[~2012-05-13 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 1:21 [PATCH 2/2] lib/bb/siggen.py: ensure dumped signatures have group R/W Joshua Lock
2012-05-13 19:02 ` Richard Purdie [this message]
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=1336935771.2711.22.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=josh@linux.intel.com \
/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