From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: "Nico Müller" <nicomueller1991@gmail.com>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH 0/2] git/gitsm do_clean fixes
Date: Fri, 24 Mar 2023 12:31:47 +0100 [thread overview]
Message-ID: <CANNYZj86dCZhkV+7CzyF09=EJBEtBzLOQWRwP=x_5uK3NCBBkw@mail.gmail.com> (raw)
In-Reply-To: <21387.1679656649236932073@lists.yoctoproject.org>
Yes, there is a strict 'master first' policy to avoid losing patches
from old branches and general chaos.
I would suggest this sequence:
- set up a master build, verify that the issue still exists
- rebase the patches into it, verify that the issue no longer exists
- adjust the commit messages, showing how the issue can be observed,
and what the patch does so that it no longer happens
- submit to bitbake-devel
Alex
On Fri, 24 Mar 2023 at 12:17, "Nico Müller <nicomueller1991@gmail.com> wrote:
>
> Okay Alex, I will resubmit the patches to `bitbake-devel`.
>
> The patches are created on dunfell. I checked the relevant master source files and the issue definitely persists there too.
> Would you suggest to rebase the patches before submitting them again?
>
> Best Regards,
> Nico
>
>
prev parent reply other threads:[~2023-03-24 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:23 [PATCH 0/2] git/gitsm do_clean fixes nicomueller1991
2023-03-24 10:23 ` [PATCH 1/2] bitbake: fetch2/git: Clean all mirrortarballs "Nico Müller
2023-03-24 10:23 ` [PATCH 2/2] bitbake: fetch2/gitsm: Add clean function "Nico Müller
2023-03-24 10:31 ` [poky] [PATCH 0/2] git/gitsm do_clean fixes Alexander Kanavin
2023-03-24 11:17 ` "Nico Müller
2023-03-24 11:31 ` 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='CANNYZj86dCZhkV+7CzyF09=EJBEtBzLOQWRwP=x_5uK3NCBBkw@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=nicomueller1991@gmail.com \
--cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).