[OpenWrt-Devel] Patchwork and git send-email

[Jeff Kletsky]

How does one get Patchwork to properly associate an update or addendum
to an existing patch / series when sent from git send-email?


While I have set --in-reply-to=''
and see the In-Reply-To and References headers both prior to sending
as well as in the delivered messages, Patchwork failed to associate
the messages with the existing patch series.


Would someone share a set of command-line arguments and a manner for
selecting their parameters that consistently works to:

* Have the "cover letter" included in the patch series

* Update an existing patch

* Add an additional patch to an existing patch series


It seems that, at least at one time, sending patches to the mailing
list was preferred over pull requests on GitHub. Is this still the
case?

Jeff


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork

[Etienne Champetier]

Hi All,

2018-01-18 1:30 GMT-08:00 Piotr Dymacz :
> Hi,
>
> On 18.01.2018 09:44, Jo-Philipp Wich wrote:
>>
>> Hi John, Alex,
>>
>> I have no problem with closing / autorejecting open tickets in patchwork
>> as long as they somehow remain available for future reference.
>
>
> ACK.
>
> Would it be possible to send the author short message why the patch was auto
> closed/rejected (excluding the auto message from patchwork)?
>
>>> To add here. Would it be possible/desire-able to add an auto-timeout
>>> to patchwork & github PRs, issues to close after X time ? Maybe make
>>> it official as part of the submission process.
>>
>>
>> I would very much like that and have been thinking about this various
>> times, maybe it is time to finally implement it.

For github PRs you might be interrested in https://github.com/probot/stale

>>
>> I could think of an idle timeout ranging somewhere between 3 to 6 months.
>
>
> Some of us discussed this during the OpenWrt Summit and IIRC we agreed that
> it would make sense and is desirable.
>
> Also, a nice message explaining why this happens, maybe with short list of
> what the user can/should do afterwards, would save us time answering the
> same questions, especially on GitHub.
>
> --
> Cheers,
> Piotr
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork

[Piotr Dymacz]

Hi,

On 18.01.2018 09:44, Jo-Philipp Wich wrote:

Hi John, Alex,

I have no problem with closing / autorejecting open tickets in patchwork
as long as they somehow remain available for future reference.


ACK.

Would it be possible to send the author short message why the patch was 
auto closed/rejected (excluding the auto message from patchwork)?



To add here. Would it be possible/desire-able to add an auto-timeout
to patchwork & github PRs, issues to close after X time ? Maybe make
it official as part of the submission process.


I would very much like that and have been thinking about this various
times, maybe it is time to finally implement it.

I could think of an idle timeout ranging somewhere between 3 to 6 months.


Some of us discussed this during the OpenWrt Summit and IIRC we agreed 
that it would make sense and is desirable.


Also, a nice message explaining why this happens, maybe with short list 
of what the user can/should do afterwards, would save us time answering 
the same questions, especially on GitHub.


--
Cheers,
Piotr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork

[Zoltan HERPAI]

Hi,

On Thu, 18 Jan 2018, John Crispin wrote:


Hi,

I would like to close all ~1000 un-handled patches from the last 3 years 
and only keep stuff from the last 6 months. any problem with that ?


No objections, if something was missed in the last 3 years (and is not in 
trunk already), then it'd need to be reworked anyway by the submitter. A 6 
month timeout period can work I think - the "need to rework anyway" 
applies similarly.


-w-
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork

[Jo-Philipp Wich]

Hi John, Alex,

I have no problem with closing / autorejecting open tickets in patchwork
as long as they somehow remain available for future reference.

> To add here. Would it be possible/desire-able to add an auto-timeout
> to patchwork & github PRs, issues to close after X time ? Maybe make
> it official as part of the submission process.

I would very much like that and have been thinking about this various
times, maybe it is time to finally implement it.

I could think of an idle timeout ranging somewhere between 3 to 6 months.


~ Jo
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork

[Alexandru Ardelean]

On Thu, Jan 18, 2018 at 10:31 AM, John Crispin  wrote:
> Hi,
>
> I would like to close all ~1000 un-handled patches from the last 3 years and
> only keep stuff from the last 6 months. any problem with that ?
>

To add here.
Would it be possible/desire-able to add an auto-timeout to patchwork &
github PRs, issues to close after X time ?
Maybe make it official as part of the submission process.

Reason is: they pile up ; number of stuff can be too much for the same
number of core people that have to handle them.
And I bet it can be psychologically daunting/depressing to open up
Github/patchwork and see 1000 unresolved stuff, and then people have
to work up the mood/will to start going through them.

Naturally, an auto-message can be added saying "please re-submit this
as the auto-timeout has been reached", as to reduce
offending/pissing-off people.

This can work nicely as an auto-triaging of stuff, since people will
make an effort to re-open PRs, resubmit patches.
This shows interest and effort for something to go in.

Obviously, it's just an idea/proposal.
Feel free to disagree/discard/etc :)

> John

Alex

> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] patchwork

[John Crispin]

Hi,

I would like to close all ~1000 un-handled patches from the last 3 years 
and only keep stuff from the last 6 months. any problem with that ?


    John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Patchwork patch state mysteriously changed to "Not applicable"

[Bob Ham]

Hi there,

I've received a message from patchwork saying that this patch

  http://patchwork.ozlabs.org/patch/576676/

now has the state of "Not applicable" but there are no comments and it
doesn't say who changed the status.

Is there a way for me to find out who changed the status and why?  Is
the responsibly party on this list and if so, could you explain?
Without understanding why this patch is "Not applicable" I can't
determine how to proceed with further development.

Kind regards,

Bob Ham
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Patchwork patch state mysteriously changed to "Not applicable"

[Bastian Bittorf]

* Bob Ham  [12.02.2016 11:00]:
> now has the state of "Not applicable" but there are no comments and it
> doesn't say who changed the status.

what I see is, that
'luci-app-bmx6/files/usr/lib/lua/luci/model/cbi/bmx6/main.lua' is
at least does not belong to openwrt.git - you should send a pull-request
to the github/packages where luci-app-bmx6 is maintained.

bye, bastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Patchwork patch state mysteriously changed to "Not applicable"

[John Crispin]

On 12/02/2016 10:54, Bob Ham wrote:
> Hi there,
> 
> I've received a message from patchwork saying that this patch
> 
>   http://patchwork.ozlabs.org/patch/576676/
> 
> now has the state of "Not applicable" but there are no comments and it
> doesn't say who changed the status.
> 
> Is there a way for me to find out who changed the status and why?  Is
> the responsibly party on this list and if so, could you explain?
> Without understanding why this patch is "Not applicable" I can't
> determine how to proceed with further development.
> 
> Kind regards,
> 
> Bob Ham


luci is hosted on github afaik. please post the patch there.

John

> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Patchwork patch state mysteriously changed to "Not applicable"

[John Crispin]

On 12/02/2016 11:43, Bob Ham wrote:
> On Fri, 2016-02-12 at 11:03 +0100, Bastian Bittorf wrote:
>> * Bob Ham  [12.02.2016 11:00]:
>>> now has the state of "Not applicable" but there are no comments and it
>>> doesn't say who changed the status.
>>
>> what I see is, that
>> 'luci-app-bmx6/files/usr/lib/lua/luci/model/cbi/bmx6/main.lua' is
>> at least does not belong to openwrt.git - you should send a pull-request
>> to the github/packages where luci-app-bmx6 is maintained.
> 
> Are you saying that the openwrt-devel mailing list is intended to be
> used only for patches for openwrt.git?  If so, this should be reflected
> in the documentation.  I followed the instructions here:
> 
>   https://dev.openwrt.org/wiki/SubmittingPatches
> 
> In particular, section 5 says:
> 
>   "Look in the Makefile if a MAINTAINER macro exists. If so, e-mail that
>   person. Unless you have a reason NOT to do so, always CC openwrt-devel
>lists.openwrt.org. If no maintainer is listed, send your patch to
>   the ​primary OpenWrt developer's mailing list."
> 
> 
> If the openwrt-devel mailing list is intended only for openwrt.git,
> where should patches for the feeds be sent?  GitHub is a problem.


i closed it incorrectly in that case. i have just set it back to new and
assigned it to jow.

John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Patchwork patch state mysteriously changed to "Not applicable"

[Bob Ham]

On Fri, 2016-02-12 at 11:03 +0100, Bastian Bittorf wrote:
> * Bob Ham  [12.02.2016 11:00]:
> > now has the state of "Not applicable" but there are no comments and it
> > doesn't say who changed the status.
> 
> what I see is, that
> 'luci-app-bmx6/files/usr/lib/lua/luci/model/cbi/bmx6/main.lua' is
> at least does not belong to openwrt.git - you should send a pull-request
> to the github/packages where luci-app-bmx6 is maintained.

Are you saying that the openwrt-devel mailing list is intended to be
used only for patches for openwrt.git?  If so, this should be reflected
in the documentation.  I followed the instructions here:

  https://dev.openwrt.org/wiki/SubmittingPatches

In particular, section 5 says:

  "Look in the Makefile if a MAINTAINER macro exists. If so, e-mail that
  person. Unless you have a reason NOT to do so, always CC openwrt-devel
   lists.openwrt.org. If no maintainer is listed, send your patch to
  the ​primary OpenWrt developer's mailing list."


If the openwrt-devel mailing list is intended only for openwrt.git,
where should patches for the feeds be sent?  GitHub is a problem.

Bob
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Patchwork patch state mysteriously changed to "Not applicable"

[Bob Ham]

Hi Pau,

The patch I emailed is against the master branch of the openwrt-routing
repository.  Can you apply that?

Regards,

Bob


On Fri, 2016-02-12 at 18:07 +0100, Pau wrote:
> Hello Bob.
> 
> I think it has been set as "Not applicable" because this package is part
> of the openwrt-routing feed which is managed from another group of
> volunteers. Plese, visit https://github.com/openwrt-routing
> 
> Your contribution seems to be applicable, so it will be probably
> approved. Thanks.
> 
> Cheers.
> 
> On 12/02/16 10:24, Bob Ham wrote:
> > Hi there,
> > 
> > I've received a message from patchwork saying that this patch
> > 
> >   http://patchwork.ozlabs.org/patch/576676/
> > 
> > now has the state of "Not applicable" but there are no comments and it
> > doesn't say who changed the status.
> > 
> > Is there a way for me to find out who changed the status and why?  Is
> > the responsibly party on this list and if so, could you explain?
> > Without understanding why this patch is "Not applicable" I can't
> > determine how to proceed with further development.
> > 
> > Kind regards,
> > 
> > Bob Ham
> > 
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Patchwork registration issues

[Daniel Dickinson]

Patchwork failed to send confirmation email to my email address, for the 
account cshore AND there is not password reset option, nor means to 
re-request confirmation email AND it won't let me register an already 
registered email address AND I can't login because the account is 
'inactive' (probably because 'not confirmed').


Regards,

Daniel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork has moved

[Ben Mulvihill]

Hi,

Are the patches from the old patchwork (regardless of status)
accessible anywhere? They are sometimes a useful reference.

Many thanks,

Ben 


On Wed, 2014-12-10 at 10:19 +0100, John Crispin wrote:
 Hi,
 
 patchwork has moved, to https://patchwork.ozlabs.org
 
 we would like express our thanks to Jeremy for creating and maintaining
 the patchwork project and also for being kind and hosting it for us.
 
 we are using this move to also cleanup our queue as there are ~500 old
 patches, some of which are several years old.
 
 our intent is to respond to every patch in the new patchwork and close
 all none merged patches after 2 months.
 
 if you have a patch inside the old queue that is not inside the new
 queue then please resend the patch.
 
 the new patchwork is the master effective immediately.
 
 those that had a admin account, please setup a new account and contact
 me directly so that we can set the admin flag on your new account
 
 Thanks,
   John
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork has moved

[Hannu Nyman]

Old patches seem to be quite intact at the old patchwork site, if you use 
directly the address to the patch list itself:

http://patchwork.openwrt.org/project/openwrt/list/

(plain patchwork.openwrt.org address seems to get redirected to the new site 
at ozlabs)



On 19.12.2014 17:09, Ben Mulvihill wrote:

Hi,

Are the patches from the old patchwork (regardless of status)
accessible anywhere? They are sometimes a useful reference.


On Wed, 2014-12-10 at 10:19 +0100, John Crispin wrote:

Hi,

patchwork has moved, to https://patchwork.ozlabs.org



___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork has moved

[Ben Mulvihill]

Brilliant, exactly what I was looking for. Thank you!

On Fri, 2014-12-19 at 17:29 +0200, Hannu Nyman wrote:
 Old patches seem to be quite intact at the old patchwork site, if you use 
 directly the address to the patch list itself:
 http://patchwork.openwrt.org/project/openwrt/list/
 
 (plain patchwork.openwrt.org address seems to get redirected to the new site 
 at ozlabs)
 
 
 On 19.12.2014 17:09, Ben Mulvihill wrote:
  Hi,
 
  Are the patches from the old patchwork (regardless of status)
  accessible anywhere? They are sometimes a useful reference.
 
 
  On Wed, 2014-12-10 at 10:19 +0100, John Crispin wrote:
  Hi,
 
  patchwork has moved, to https://patchwork.ozlabs.org
 
 
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] patchwork has moved

[John Crispin]

Hi,

patchwork has moved, to https://patchwork.ozlabs.org

we would like express our thanks to Jeremy for creating and maintaining
the patchwork project and also for being kind and hosting it for us.

we are using this move to also cleanup our queue as there are ~500 old
patches, some of which are several years old.

our intent is to respond to every patch in the new patchwork and close
all none merged patches after 2 months.

if you have a patch inside the old queue that is not inside the new
queue then please resend the patch.

the new patchwork is the master effective immediately.

those that had a admin account, please setup a new account and contact
me directly so that we can set the admin flag on your new account

Thanks,
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Patchwork seems to be dead (Internal server error - 500)

[Jiri Slachta]

Hello everyone,

just to let you know, patchwork.openwrt.org seems to be dead - Internal server 
error - http status code 500.

Jiri
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork for openwrt

[Raphaël HUCK]

Le Fri, 07 May 2010 12:24:29 +0200,
j...@phrozen.org a écrit :

 Hi,
 
 http://patchwork.cyranjo.org
 
 John
 
 

Hi John,

this is great! But why not http://patchwork.openwrt.org?

Also a problem with patchwork is that it exposes email adresses to
anyone with simple mailto: links in clear.

Cheers,

-Raphael
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork for openwrt

[Quentin Armitage]

On Mon, 2010-05-10 at 10:44 +0200, j...@phrozen.org wrote:
 Quoting Raphaël HUCK r...@cksum.org:
 
  Le Fri, 07 May 2010 12:24:29 +0200,
  j...@phrozen.org a écrit :
 
  Hi,
 
  http://patchwork.cyranjo.org
 
  John
 
 
 
This is really excellent.

It would be really good if it could also incorporate patches submitted
in tickets to the trac system. A number of people, myself included, try
to include a patch when reporting a bug/issue/feature on the trac
system, and at the moment those won't be included in the patchwork
view. 

Quentin


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork for openwrt

[john]

Yes, great idea.

i will be in berlin at the wcw on the weekend. there i will be meeting  
CyrusFF who is currently hosting the patchwork installation. i will  
then discuss next steps with him and also talk to bartman/kaloz about  
a dns entry pointing at that ip


i'll keep you updated.


--
John Crispin
hacking, coding, etc
blogic on irc

   ___ __
  |   |.-.-.-.|  |  |  |..|  |_
  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
  |___||   __|_|__|__||||__|  ||
   |__| W I R E L E S S   F R E E D O M
  KAMIKAZE (bleeding edge) ---
   * 10 oz Vodka   Shake well with ice and strain
   * 10 oz Triple sec  mixture into 10 shot glasses.
   * 10 oz lime juice  Salute!
  ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork for openwrt

[john]

we already have one running



Quoting Jeremy Kerr j...@ozlabs.org:


Hello,


 Hello
 Is there any chance we could set up a patchwork server like the one
 the kernel has?
 I'm not sure, how much work this will be, but there are a significant
 number of patches send to openwrt-devel, which are more or less
 silently ignored, which is not very nice to the authors and probably
 even worse for the openwrt project itself.
 Having an easy way to list patches and thier status could help with
 that.

I totally agree with you Bernhard.

The code for patchwork is available here:
http://ozlabs.org/~jk/projects/patchwork/


I can set up an instance on patchwork.ozlabs.org if you like, just   
let me know

who the maintainers should be.

Cheers,


Jeremy
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel





--
John Crispin
hacking, coding, etc
blogic on irc

   ___ __
  |   |.-.-.-.|  |  |  |..|  |_
  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
  |___||   __|_|__|__||||__|  ||
   |__| W I R E L E S S   F R E E D O M
  KAMIKAZE (bleeding edge) ---
   * 10 oz Vodka   Shake well with ice and strain
   * 10 oz Triple sec  mixture into 10 shot glasses.
   * 10 oz lime juice  Salute!
  ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] patchwork for openwrt

[Bernhard Loos]

Hello
Is there any chance we could set up a patchwork server like the one
the kernel has?
I'm not sure, how much work this will be, but there are a significant
number of patches send to openwrt-devel, which are more or less
silently ignored, which is not very nice to the authors and probably
even worse for the openwrt project itself.
Having an easy way to list patches and thier status could help with that.

Bernhard
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork for openwrt

[Raphaël HUCK]

Le Thu, 6 May 2010 12:19:34 +0200,
Bernhard Loos bernhardl...@googlemail.com a écrit :

 Hello
 Is there any chance we could set up a patchwork server like the one
 the kernel has?
 I'm not sure, how much work this will be, but there are a significant
 number of patches send to openwrt-devel, which are more or less
 silently ignored, which is not very nice to the authors and probably
 even worse for the openwrt project itself.
 Having an easy way to list patches and thier status could help with
 that.


I totally agree with you Bernhard.

The code for patchwork is available here:
http://ozlabs.org/~jk/projects/patchwork/

It is built on the django web framework, which is Python-based, as Trac.

Several serious projects are using it:

https://patchwork.kernel.org
http://patchwork.linux-mips.org
http://patchwork.openembedded.org
http://patchwork.coreboot.org


-Raphael
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] patchwork for openwrt

[Bernhard Loos]

From: Bernhard Loos bernhardl...@googlemail.com
Date: 2010/5/6
Subject: Re: [OpenWrt-Devel] patchwork for openwrt
To: Outback Dingo outbackdi...@gmail.com


well, there is this:
https://lists.openwrt.org/pipermail/openwrt-devel/2010-May/007019.html
then this: 
https://lists.openwrt.org/pipermail/openwrt-devel/2010-April/006960.html
https://lists.openwrt.org/pipermail/openwrt-devel/2010-April/006934.html

There aren't that many, but still ...

Maybe it would be better to have some script open trac tickets for
patches send to the mailinglist, I'm not sure.

 Bernhard

2010/5/6 Outback Dingo outbackdi...@gmail.com:
 what patches specifically are you referrng

 On Thu, May 6, 2010 at 6:19 AM, Bernhard Loos bernhardl...@googlemail.com
 wrote:

 Hello
 Is there any chance we could set up a patchwork server like the one
 the kernel has?
 I'm not sure, how much work this will be, but there are a significant
 number of patches send to openwrt-devel, which are more or less
 silently ignored, which is not very nice to the authors and probably
 even worse for the openwrt project itself.
 Having an easy way to list patches and thier status could help with that.

            Bernhard
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork for openwrt

[john]

we have been testing patchwork internally for 3-4 weeks now, i thinki  
we can make it public now, let me talk to the right people and see  
what we can do .




Quoting Raphaël HUCK r...@cksum.org:


Le Thu, 6 May 2010 12:19:34 +0200,
Bernhard Loos bernhardl...@googlemail.com a écrit :


Hello
Is there any chance we could set up a patchwork server like the one
the kernel has?
I'm not sure, how much work this will be, but there are a significant
number of patches send to openwrt-devel, which are more or less
silently ignored, which is not very nice to the authors and probably
even worse for the openwrt project itself.
Having an easy way to list patches and thier status could help with
that.



I totally agree with you Bernhard.

The code for patchwork is available here:
http://ozlabs.org/~jk/projects/patchwork/

It is built on the django web framework, which is Python-based, as Trac.

Several serious projects are using it:

https://patchwork.kernel.org
http://patchwork.linux-mips.org
http://patchwork.openembedded.org
http://patchwork.coreboot.org


-Raphael
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel





--
John Crispin
hacking, coding, etc
blogic on irc

   ___ __
  |   |.-.-.-.|  |  |  |..|  |_
  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
  |___||   __|_|__|__||||__|  ||
   |__| W I R E L E S S   F R E E D O M
  KAMIKAZE (bleeding edge) ---
   * 10 oz Vodka   Shake well with ice and strain
   * 10 oz Triple sec  mixture into 10 shot glasses.
   * 10 oz lime juice  Salute!
  ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] patchwork for openwrt

[Jeremy Kerr]

Hello,

  Hello
  Is there any chance we could set up a patchwork server like the one
  the kernel has?
  I'm not sure, how much work this will be, but there are a significant
  number of patches send to openwrt-devel, which are more or less
  silently ignored, which is not very nice to the authors and probably
  even worse for the openwrt project itself.
  Having an easy way to list patches and thier status could help with
  that.
 
 I totally agree with you Bernhard.
 
 The code for patchwork is available here:
 http://ozlabs.org/~jk/projects/patchwork/

I can set up an instance on patchwork.ozlabs.org if you like, just let me know 
who the maintainers should be.

Cheers,


Jeremy
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel