From: Peter Seebach <peter.seebach@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] pseudo: handle fchmodat better, mask out unwanted write bits
Date: Wed, 21 May 2014 13:58:23 -0500 [thread overview]
Message-ID: <20140521135823.09df4ad0@e6410-2> (raw)
In-Reply-To: <537CC2C6.1040503@linux.intel.com>
On Wed, 21 May 2014 08:14:14 -0700
Saul Wold <sgw@linux.intel.com> wrote:
> Peter, I know it says Backport above, but can you please add an
> Upstream-Status: tag to this .patch file.
I might be able to, but I'm sort of swamped right now; I will see if I can
shake some minutes loose. Do Upstream-Status tags have a specified format?
> Also, do you have plans to do a 1.6 update for OE-Core soon?
I would love to, but I don't have an ETA on actually having any available
time. I'd like to clean up a few more things, but the 1_6_0 branch seems
pretty stable these days, I think. Although I'd like more testing with the
xattr support.
I think I heard something about something being done in early to mid June
after which I might have cycles.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2014-05-21 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 21:51 [PATCH 0/1] pseudo permissions: better fchmodat, mask out write bits Peter Seebach
2014-05-19 21:51 ` [PATCH 1/1] pseudo: handle fchmodat better, mask out unwanted " Peter Seebach
2014-05-21 15:14 ` Saul Wold
2014-05-21 18:58 ` Peter Seebach [this message]
2014-05-21 19:00 ` Burton, Ross
2014-05-21 23:08 ` Peter Seebach
-- strict thread matches above, loose matches on Subject: below --
2014-05-21 23:12 [PATCH 0/1] Revised pseudo-fchmodat (updated upstream-status) Peter Seebach
2014-05-21 23:12 ` [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=20140521135823.09df4ad0@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@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 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.