From: Peter Seebach <peter.seebach@windriver.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Revised pseudo-fchmodat (updated upstream-status)
Date: Wed, 21 May 2014 18:12:32 -0500 [thread overview]
Message-ID: <cover.1400713858.git.peter.seebach@windriver.com> (raw)
This is the pseudo-fchmodat patch, same code, but with an upstream-status
thing to indicate that it's a backport. (Slightly complicated because this
was three patches in the upstream branch, and I just merged in the combined
results so it'd be easier to see what was happening, and no one would have
to review a patch and reject it for obvious bugs that are fixed in the
next patch.)
The following changes since commit f1727bb18f35ff01e53d3d442a6ff3c613639fa6:
guile: Update to 2.0.11 version (2014-05-21 10:50:37 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/pseudo-fchmodat2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo-fchmodat2
Peter Seebach (1):
pseudo: handle fchmodat better, mask out unwanted write bits
.../pseudo/files/pseudo-fchmodat-permissions.patch | 107 ++++++++++++++++++++
meta/recipes-devtools/pseudo/pseudo_1.5.1.bb | 3 +-
2 files changed, 109 insertions(+), 1 deletions(-)
create mode 100644 meta/recipes-devtools/pseudo/files/pseudo-fchmodat-permissions.patch
next reply other threads:[~2014-05-21 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 23:12 Peter Seebach [this message]
2014-05-21 23:12 ` [PATCH 1/1] pseudo: handle fchmodat better, mask out unwanted write bits Peter Seebach
2014-05-27 19:01 ` WARNING: FILES GETTING MARKED WORLD-WRITEABLE. (Was: Re: [PATCH 1/1] pseudo: handle fchmodat better, mask out unwanted write bits) Peter Seebach
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=cover.1400713858.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox