From: Jiajie Hu <jiajie.hu@intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] devtool: execute associated functions while preparing the source tree
Date: Tue, 29 Nov 2016 15:37:26 +0800 [thread overview]
Message-ID: <1745772.zAqL5B44bX@jiajiehu> (raw)
In-Reply-To: <CABcZANmmXvVNTiozc_y-i+efy7JZGphPezgbBRS8fZKfdtYnVA@mail.gmail.com>
On Monday, November 28, 2016 11:04:40 PM Christopher Larson wrote:
> This will do the commit after the first postfunc is done, so won’t the
> changes from the main func and the first postfunc both be included in that
> commit?
I suppose all changes from the main func have already been committed in
exec_func. As an example, `devtool modify x11vnc`, where x11vnc comes from
meta-oe, seems to work as expected.
next prev parent reply other threads:[~2016-11-29 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 2:59 [PATCH] devtool: execute associated functions while preparing the source tree Jiajie Hu
2016-11-29 6:04 ` Christopher Larson
2016-11-29 7:37 ` Jiajie Hu [this message]
2016-11-29 18:01 ` Paul Eggleton
2016-11-30 1:33 ` Jiajie Hu
2016-11-30 1:39 ` Paul Eggleton
2016-11-30 3:14 ` Paul Eggleton
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=1745772.zAqL5B44bX@jiajiehu \
--to=jiajie.hu@intel.com \
--cc=clarson@kergoth.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