From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Yoann Congal <yoann.congal@smile.fr>,
Yocto Mailing list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Git repo setup for Yocto upstream contribution
Date: Mon, 9 Jan 2023 19:23:28 +0100 [thread overview]
Message-ID: <Y7xboMQghF3h1WVT@mail.local> (raw)
In-Reply-To: <CANNYZj_ctBSuQG-_rjD8STSmcVCK__DJF-Rg4ngyrNmYgN5N5w@mail.gmail.com>
On 09/01/2023 10:29:13+0100, Alexander Kanavin wrote:
> I've been making patches against an integrated poky checkout for many
> years, including bitbake patches. They're usually correctly picked up
> and applied; you only need to ensure you route them to correct mailing
> lists.
>
No, please send patches against the correct git tree, else you are
putting more load on the maintainers than necessary.
This was the cause of:
https://lore.kernel.org/all/Y5Sr9HSWIc5LVzl9@mail.local/
This can silently fail and then you need to wait for 7hours for the AB
to fail and this delays testing for one more day.
> Alex
>
> On Sat, 7 Jan 2023 at 14:05, Yoann Congal <yoann.congal@smile.fr> wrote:
> >
> > Hi,
> >
> > Since I plan to work regularly on upstream Yocto and contributing, I
> > wonder about the best way to best setup my git repos to do that...
> >
> > I've started with the upstream poky repo but when I make a commit on,
> > for example, bitbake, my patch applies on a bitbake/some-path file which
> > does not exist in the bitbake repo (only "some-path" exists in the
> > bitbake repo).
> >
> > Is this something I should address ? I found some patches for bitbake in
> > the mailing list that are for "bitbake/..." paths... So, maybe, basing
> > my patches on the poky repo is totally OK for now...?
> >
> > To the Yocto maintainers, how do you manage this (poky repo, combo-layer
> > and individual bitbake/doc/meta-yocto repo) ?
> >
> > Note: I have found the "combo-layer splitpatch" tool but it does not
> > look like a full solution... Maybe I'm missing something?
> >
> > Thanks!
> > --
> > Yoann Congal ("yocton" on IRC)
> > Smile ECS - Tech Expert
> >
> >
> >
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#58940): https://lists.yoctoproject.org/g/yocto/message/58940
> Mute This Topic: https://lists.yoctoproject.org/mt/96112311/3617179
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-01-09 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 13:05 Git repo setup for Yocto upstream contribution Yoann Congal
2023-01-09 9:29 ` [yocto] " Alexander Kanavin
2023-01-09 12:07 ` Yoann Congal
2023-01-09 18:23 ` Alexandre Belloni [this message]
2023-01-09 18:30 ` Alexander Kanavin
2023-01-09 19:16 ` Alexandre Belloni
2023-01-10 14:54 ` Alexander Kanavin
2023-01-10 15:02 ` Alexandre Belloni
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=Y7xboMQghF3h1WVT@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=yoann.congal@smile.fr \
--cc=yocto@lists.yoctoproject.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.