From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Re-enable custom preference dialog responder
Date: Wed, 14 Sep 2011 16:35:27 -0700 [thread overview]
Message-ID: <cover.1316043111.git.josh@linux.intel.com> (raw)
When disabling code in an earlier commit[1] I'd accidentally disabled the custom
response callback that forced a re-parse after changing certain preferences.
The following patch re-enables this code.
Regards,
Joshua
1. http://git.openembedded.org/cgit.cgi/bitbake/commit/?id=3157967d08266b8d1ac563ba609ac3027b60d040
The following changes since commit f4be83aae77a713e2b5a2d094651639b6e641031:
hob: correctly set the selected image when loading a recipe (2011-09-13 08:30:49 -0700)
are available in the git repository at:
git://github.com/incandescant/bitbake hob
https://github.com/incandescant/bitbake/tree/hob
Joshua Lock (1):
ui/crumbs/hobprefs: re-enable reloading of data after prefs changes
lib/bb/ui/crumbs/hobprefs.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
1.7.6
next reply other threads:[~2011-09-14 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 23:35 Joshua Lock [this message]
2011-09-14 23:35 ` [PATCH 1/1] ui/crumbs/hobprefs: re-enable reloading of data after prefs changes Joshua Lock
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.1316043111.git.josh@linux.intel.com \
--to=josh@linux.intel.com \
--cc=bitbake-devel@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