[yocto] [OE-core] [oe] Git commit process question.

akuster808 akuster808 at gmail.com
Wed Apr 3 04:38:57 PDT 2019

On 4/3/19 3:38 AM, Alexander Kanavin wrote:
> Just to make clear, the AUH workflow does require the maintainer to
> sign off and edit a commit message via 'git commit -s --reset-author
> --amend' for every commit, 
Not sure if this a requirement anymore. Most of my packages got updated
by other folks this time around.  Hard to say if the AUH played a part
or are folks now using the devtool check.
> so AUH does not get in the way of useful
> commit messages.
There was talk of using the AUH to fast track updates that pass the
process so in that case the message would be whatever the AUH provides

- armin
> Alex
> On Wed, 3 Apr 2019 at 12:31, Burton, Ross <ross.burton at intel.com> wrote:
>> On Tue, 2 Apr 2019 at 20:46, Tom Rini <trini at konsulko.com> wrote:
>> pr
>>>> The kernel does not have "upgrade foo to the latest upstream version" commits.
>>>> With the Automatic Upgrade Helper this is a semi-automatic task, and
>>>> most of the time there is no specific motivation other than upgrading
>>>> to the latest upstream version.
>>> But since that's just filling in a template the body can also be a
>>> template perhaps with useful AUH data (run at ... by ... ?) ?
>> Apart from making the commit message longer what does this achieve?
>> The commit already has a timestamp and author.
>> Ross
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core

More information about the yocto mailing list