patchwork

patchwork

[Chris Mason]

Hello everyone,

I've asked the kernel.org admins to setup patchwork tracking for the
btrfs mailing list.  This is a pretty cool tool that tracks patches sent
to the list and makes it easy to download and apply them.

I'll be the main consumer of this, but you can check out the interface
at:

http://patchwork.kernel.org/project/linux-btrfs/list/

-chris

Patchwork

[Ralf Baechle]

Many of you may already have heared about it - I've installed patchwork
on http://patchwork.linux-mips.org.  The system is now running mostly
flawless so time to announce it.

What is patchwork?

Patchwork is a patch tracking system.  It is subscribed to the linux-mips
mailing list and automatically sifts throuogh the list for patches posted.
The web interface allows anybody to see which patches are still pending,
are under review, have been applied or rejected.

Patchwork also keeps track of replies to patches so it's often easier to
follow than by using a mail reader.  Patchworks also collects Acked-by:,
Signed-off-By: lines so when downloading a patch from the web interface
the log messages will have been updated to contain the updated tags.

Why is patchwork a good thing?

It allows a maintainer to keep a good overview over all the pending patches.
Unlike many previous systems that were implemented or suggested it doesn't
get into the way of established patch submission and handling practices
but rather provides a tool to automate a part of necessary procedures.

What does patchworks mean for patch submissions?

Patchwork is subscribed to the linux-mips mailing list.  So it will only
keep track of patches that have been posted to the linux-mips mailing list
but not of patches that have been sent in private to me.  This is a problem
so I'm considering to reject patches that have not been submitted to the
mailing list as a matter of policy.

Beyond that it's largely up to the patch submitter.  For a submitter who
doesn't use patchwork things will work the same way they used to work.

What new advanced features deos patchwork offer to submitters?

Submitters can create an account on patchworks.  They can change the
status of their patches - which are identified as theirs by the submitter's
email address - for example when they wish withdraw a patch because it
was found faulty or are about to send a better revision.

There is also a feature to create patch bundles from several patches which
then can be downloaded as a single download.

Which patches are tracked in patchworks?

I've installed patchworks about four weeks ago.  For testing purposes and
also to ensure I've not dropped anything on the floor I've fed the
mailing list archives back to June 2009 into patchworks, then manually
walked through the hundreds of patches to ensure all patches have been
handled.

If you've sent patches that have not been applied yet and don't show up
in patchworks as new or under review, then please resent your patches.

  Ralf

Patchwork

[Konrad Mattheis]

Hi,

I found a lot of nice patches from ulf samuelson for the new at91sam9g45 in the patchwork.
What is the usual way, that they get included.


bye
Konrad

Re: Patchwork

[Philip Balister]

On 04/15/2010 01:56 PM, Konrad Mattheis wrote:
> Hi,
>
> I found a lot of nice patches from ulf samuelson for the new at91sam9g45 in the patchwork.
> What is the usual way, that they get included.

If you test them send a suitable Acked-by to the list.

Philip

>
>
> bye
> Konrad
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Patchwork

[Ralf Baechle]

Account creation in patchwork was broken a long time ago and some unrelated
bug had caused a ugly junk in the listings of patches that contain
non-ASCII characters.  I've fixed both along with upgrading patchwork to
the latest and greatest version.

What this mean:

 - the junk names displayed in the listings is gone
 - you can create new patchwork accounts and use those accounts for example
   to administrate your own patches, for example when submitting a new
   version or when you discover a bug and want to withdraw a patch.

The upgrade went more than rough and involved lots of manual database
patching.  If something doesn't work right, please let me know.

Happy patchworking!

  Ralf

patchwork

[John Crispin]

Hi Jeremy,

could you kindly setup a patchwork for the ath11k list ?

     John


_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: patchwork

[Kalle Valo]

John Crispin <john@phrozen.org> writes:

> could you kindly setup a patchwork for the ath11k list ?

I already requested kernel.org admins to setup one but I have not heard
back yet.

-- 
Kalle Valo

_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: patchwork

[Jeremy Kerr]

Hi John and Kalle,

> > could you kindly setup a patchwork for the ath11k list ?
> 
> I already requested kernel.org admins to setup one but I have not
> heard
> back yet.

I'm happy to do so for ozlabs.org, but don't want to duplicate with a
kernel.org setup. Let me know what you want to do here.

If you do want to go ahead, just let me know what name you want to use
for the instance ("ath11k development"?), and the patchwork usernames of
those you want to assign as maintainers.

Cheers,


Jeremy


_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: patchwork

[Kalle Valo]

Jeremy Kerr <jk@ozlabs.org> writes:

> Hi John and Kalle,
>
>> > could you kindly setup a patchwork for the ath11k list ?
>> 
>> I already requested kernel.org admins to setup one but I have not
>> heard
>> back yet.
>
> I'm happy to do so for ozlabs.org, but don't want to duplicate with a
> kernel.org setup. Let me know what you want to do here.

As I already use patchwork.kernel.org with wireless-drivers patches, and
use a custom patchwork script[1], I would prefer to use
patchwork.kernel.org also with ath11k. For example, in case there are
API incompatibilities etc.

> If you do want to go ahead, just let me know what name you want to use
> for the instance ("ath11k development"?), and the patchwork usernames of
> those you want to assign as maintainers.

What if we'll wait for kernel.org admins for a week or so still (I sent
the request on April 13th, I'll ping them) and if I don't hear back,
maybe then you could add it to ozlabs? I'll let you know how it goes.

And BTW thanks for implementing patchwork, it's just awesome! I use it
daily, makes my life so much easier :)

[1] https://github.com/kvalo/pwcli

-- 
Kalle Valo

_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

patchwork

[akuster808]

Hello OE folk,

My apologies for cross posting.

Who is the Admin for Patchwork?

I would like additional privileges to manage the "Yocto Project Layers"
queue.

Also, I would like additional  privileges to add new branches for any
oe, meta-oe queues & yp layers.

kind regards,
Armin

Re: patchwork

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Jeremy Kerr <jk@ozlabs.org> writes:
>
>> Hi John and Kalle,
>>
>>> > could you kindly setup a patchwork for the ath11k list ?
>>> 
>>> I already requested kernel.org admins to setup one but I have not
>>> heard
>>> back yet.
>>
>> I'm happy to do so for ozlabs.org, but don't want to duplicate with a
>> kernel.org setup. Let me know what you want to do here.
>
> As I already use patchwork.kernel.org with wireless-drivers patches, and
> use a custom patchwork script[1], I would prefer to use
> patchwork.kernel.org also with ath11k. For example, in case there are
> API incompatibilities etc.
>
>> If you do want to go ahead, just let me know what name you want to use
>> for the instance ("ath11k development"?), and the patchwork usernames of
>> those you want to assign as maintainers.
>
> What if we'll wait for kernel.org admins for a week or so still (I sent
> the request on April 13th, I'll ping them) and if I don't hear back,
> maybe then you could add it to ozlabs? I'll let you know how it goes.

The admins now created a project for us:

https://patchwork.kernel.org/project/ath11k/list/

-- 
Kalle Valo

_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: patchwork

[akuster808]

ok, so no Admins. This is unexceptionable.

OE TSC and Board, I believe its your time to get involved.

regards,
Armin

On 5/3/19 10:18 AM, akuster808 wrote:
> Hello OE folk,
>
> My apologies for cross posting.
>
> Who is the Admin for Patchwork?
>
> I would like additional privileges to manage the "Yocto Project Layers"
> queue.
>
> Also, I would like additional  privileges to add new branches for any
> oe, meta-oe queues & yp layers.
>
> kind regards,
> Armin
>

Re: patchwork

[Zoran Stojsavljevic]

Off Topic @: The same chaos as with German Govt. (KVR and Finanzamt).

Zoran
_______

On Sun, May 12, 2019 at 8:05 PM akuster808 <akuster808@gmail.com> wrote:
>
> ok, so no Admins. This is unexceptionable.
>
> OE TSC and Board, I believe its your time to get involved.
>
> regards,
> Armin
>
> On 5/3/19 10:18 AM, akuster808 wrote:
> > Hello OE folk,
> >
> > My apologies for cross posting.
> >
> > Who is the Admin for Patchwork?
> >
> > I would like additional privileges to manage the "Yocto Project Layers"
> > queue.
> >
> > Also, I would like additional  privileges to add new branches for any
> > oe, meta-oe queues & yp layers.
> >
> > kind regards,
> > Armin
> >
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: patchwork

[Mark Hatle]

On 5/12/19 9:04 PM, akuster808 wrote:
> ok, so no Admins. This is unexceptionable.
> 
> OE TSC and Board, I believe its your time to get involved.

I've not used patchwork before, do you know who originally configured it?  Was
it Paul Eggleton, or Richard, or?  If I have an idea who was originally
responsible, I'm pretty sure we can figure out a handoff plan to someone else.

--Mark

> regards,
> Armin
> 
> On 5/3/19 10:18 AM, akuster808 wrote:
>> Hello OE folk,
>>
>> My apologies for cross posting.
>>
>> Who is the Admin for Patchwork?
>>
>> I would like additional privileges to manage the "Yocto Project Layers"
>> queue.
>>
>> Also, I would like additional  privileges to add new branches for any
>> oe, meta-oe queues & yp layers.
>>
>> kind regards,
>> Armin
>>
> 

Patchwork

[Ryan Eatmon]

All,

We are using the new Yocto Project Patchwork server to track the state 
of patches sent to this mailing list.  If you would like to know the 
status of a given patch, you may query the project at:

https://patchwork.yoctoproject.org/project/arago/list/


-- 
Ryan Eatmon
reatmon@ti.com

Patchwork

[Ryan Eatmon]

All,

We are using the new Yocto Project Patchwork server to track the state 
of patches sent to this mailing list.  If you would like to know the 
status of a given patch, you may query the project at:

https://patchwork.yoctoproject.org/project/ti/list/


-- 
Ryan Eatmon
reatmon@ti.com