From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] devtool: add license checksum change handling to 'devtool upgrade'
Date: Wed, 29 Nov 2017 11:57:36 +0200 [thread overview]
Message-ID: <5e7391dc-a3fe-24de-ac7e-d93bfe1a19a6@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaXiuPjXBH4PZ6PDASmiSz=r06sFNXMvZm9-NUKwngSig@mail.gmail.com>
On 11/29/2017 11:10 AM, Burton, Ross wrote:
> I just tested this new behaviour and I for one like how it worked. It's
> sufficiently verbose that it obviously needs to be deleted and is
> stashed somewhere useful.
FWIW, I will modify AUH so that it will move the info from recipe into
commit, when creating one. So then a human will only need to amend the
commit message. The broader goal is to automate the upgrade process as
much as possible, give the commits directly to autobuilder and post them
to oe-core list, and if they pass and don't need amending, I think it's
fine to push them to straight to master with the 'From' still containing
a robot name :)
So that I (and other recipe maintainers) can spend time on more
interesting things.
> A new patchtest test to automatically tell people if they left it in the
> recipe would be good too.
Yes; will be done after I'm happy with the way AUH works :)
Alex
prev parent reply other threads:[~2017-11-29 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 14:54 [PATCH] devtool: add license checksum change handling to 'devtool upgrade' Alexander Kanavin
2017-11-27 18:11 ` Khem Raj
2017-11-27 19:23 ` Alexander Kanavin
2017-11-29 7:43 ` Khem Raj
2017-11-29 8:07 ` Alexander Kanavin
2017-11-29 9:10 ` Burton, Ross
2017-11-29 9:57 ` Alexander Kanavin [this message]
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=5e7391dc-a3fe-24de-ac7e-d93bfe1a19a6@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox