From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] pseudo 1.5.1
Date: Wed, 27 Feb 2013 15:19:00 -0600 [thread overview]
Message-ID: <cover.1361999203.git.peter.seebach@windriver.com> (raw)
It turns out that I forgot the part where it would be useful to be
able to temporarily suppress the suppression of fsync()-type calls.
Also the documentation had bitrotted (no references to FASTOP or to
the fsync stuff, or to some other changes), so I fixed a few obvious
gaps.
This should have no immediate functional change on anything in oe-core,
but it allows for specifying
PSEUDO_ALLOW_FSYNC=1 <command>
and getting fsync behavior from that command.
There's also a performance improvement in the case where NDEBUG is
defined, which is "never" in our context.
This is a lowish-priority change for oe-core, and in any event I don't
believe the tarballs are up on the Yocto servers yet, but we need it
internally and paperwork's easier if I submit it and then backport it.
(I do recommmend it, though, because this makes it a LOT easier to
check whether the fsync behavior is affecting something.)
The following changes since commit 8e69f0ea42505e8f703893e18d73658b83d3b046:
Constantin Musca (1):
augeas: change SRC_URI
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/pseudo151
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo151
Peter Seebach (1):
Update pseudo to 1.5.1
.../pseudo/{pseudo_1.5.bb => pseudo_1.5.1.bb} | 4 ++--
meta/recipes-devtools/pseudo/pseudo_git.bb | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/pseudo/{pseudo_1.5.bb => pseudo_1.5.1.bb} (52%)
next reply other threads:[~2013-02-27 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 21:19 Peter Seebach [this message]
2013-02-27 21:19 ` [PATCH 1/1] Update pseudo to 1.5.1 Peter Seebach
2013-02-28 4:53 ` [PATCH 0/1] pseudo 1.5.1 Saul Wold
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.1361999203.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 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.