[bitbake-devel] [OE-core] should we switch off patchwork for oe-core and bitbake projects
raj.khem at gmail.com
Wed Feb 1 20:36:48 CET 2012
On Wed, Feb 1, 2012 at 10:19 AM, Martin Jansa <martin.jansa at gmail.com> wrote:
> On Wed, Feb 01, 2012 at 10:07:14AM -0800, Khem Raj wrote:
>> On Wed, Feb 1, 2012 at 9:51 AM, McClintock Matthew-B29882
>> <B29882 at freescale.com> wrote:
>> > I'm saying leave it there even if its not maintained. I can still go search
>> > for patches sent by me or other specific people.
>> thats what mailing list archives are for.
> is there something like
> for some mailing list archive?
not exactly but if we enable mbox archive download on the ml
you can see the mails in mbox formats and download it. then it would
be git am'able
> When I see some interesting patch in ML, easiest way for me to get it to
> development branch is to open patchwork web (from any computer) and then
> call pw-am.sh NUMBER in screen session on my development workstation.
> Even when reading mail in mutt on the same machine it's easier for me to
> use pw-am.sh to get that patch to my chroot for OE builds.
> And that git hook marking them as applied works very well.. so usually I
> just have to mark cover letters as applied.
yes it works fine for most of the times however for oe-core
the patches get sent to ml and then picked and again resent
as pull request sometimes nudged sometimes unmodified and patchwork
does not close them automatically.
so purpose of patchwork in this case would be different then It is just to host
the patches for oe-core but has a different usage for
oe-devel where the patches are picked and closed from the patchwork.
This could be confusing at times especially
for new people. But if we see enough value to keep it
that way then we can think of making some changes so it
detects the resends somehow if the patch hashes are not same
etc and close them.
More information about the bitbake-devel