From: Justin Bronder <jsbronder@cold-front.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: kernel-yocto: create dummy git user if necessary
Date: Fri, 9 Feb 2018 15:38:19 -0500 [thread overview]
Message-ID: <20180209203819.GA11421@lasswell> (raw)
In-Reply-To: <CADkTA4OVbFXs=oEwkZF3FiGTwXC1X-1BjRNixK3zSo1xGq1=gA@mail.gmail.com>
On 09/02/18 15:27 -0500, Bruce Ashfield wrote:
> On Fri, Feb 9, 2018 at 2:53 PM, Justin Bronder <jsbronder@cold-front.org> wrote:
> > The user's global git configuration may not have the name and email set
> > and git autodetection can fail. The initialization commit for a non-git
> > kernel directory doesn't really need to be tied back to them anyways.
> > Instead, create a user and email that's clearly tied back to
> > kernel-yocto.bbclass.
> >
> > Signed-off-by: Justin Bronder <jsbronder@cold-front.org>
> > ---
> > meta/classes/kernel-yocto.bbclass | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
> > index 60979a218f..dbf01f86b6 100644
> > --- a/meta/classes/kernel-yocto.bbclass
> > +++ b/meta/classes/kernel-yocto.bbclass
> > @@ -247,6 +247,8 @@ do_kernel_checkout() {
> > fi
> > rm -f .gitignore
> > git init
> > + git config user.name 'Yocto Kernel Git Initializer'
> > + git config user.email 'kernel-yocto.bbclass@invalid'
>
>
> This is already handled in the utility classes via the
> check_git_config routine and it is called in
> kernel-yocto's do_patch routine.
>
> If it is needed earlier (as it appears it is), move that call to
> do_kernel_checkout.
Ah, didn't see that. Thanks. I'll send a new patch shortly.
--
Justin Bronder
prev parent reply other threads:[~2018-02-09 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 19:53 [PATCH] kernel-yocto: create dummy git user if necessary Justin Bronder
2018-02-09 20:27 ` Bruce Ashfield
2018-02-09 20:38 ` Justin Bronder [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=20180209203819.GA11421@lasswell \
--to=jsbronder@cold-front.org \
--cc=bruce.ashfield@gmail.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.