[U-Boot] pending patches website
not so long ago there was some custom thingy that was running on the u-boot website that'd automatically grab patches from the mailing list and try to file them away so they wouldnt get lost. but i cant seem to find it any more. is it gone ? -mike
Hi Mike,
not so long ago there was some custom thingy that was running on the u-boot website that'd automatically grab patches from the mailing list and try to file them away so they wouldnt get lost. but i cant seem to find it any more. is it gone ?
No, it is not gone, it only starts to bitrot :(
It also never by itself grabbed patches, but the idea was to post the patches to its own email account which in turn sent acknowledgements to the mailinglist _including_ a unique tracking number which was needed for automatic handling of follow-up mail.
Unfortunately the original implementor is not available anymore and we currently do not see how to finish the missing bits, especially the automatic handling of the status of patches.
If someone on this list with (solid) Perl knowledge volunteers to pick up the strings, let me know offlist.
Cheers Detlev
[1] http://bugs.denx.de/databases/u-boot
On Thursday 02 April 2009 08:32:00 Detlev Zundel wrote:
not so long ago there was some custom thingy that was running on the u-boot website that'd automatically grab patches from the mailing list and try to file them away so they wouldnt get lost. but i cant seem to find it any more. is it gone ?
No, it is not gone, it only starts to bitrot :(
It also never by itself grabbed patches, but the idea was to post the patches to its own email account which in turn sent acknowledgements to the mailinglist _including_ a unique tracking number which was needed for automatic handling of follow-up mail.
Unfortunately the original implementor is not available anymore and we currently do not see how to finish the missing bits, especially the automatic handling of the status of patches.
If someone on this list with (solid) Perl knowledge volunteers to pick up the strings, let me know offlist.
thanks, that was the site i was looking for
maybe the lack of automation is a problem ? having a completely custom system is also a problem ...
would patchwork satisfy the same tracking needs ? benefits there are: - automation - someone else does the work of developing it - all discussion stays tied to mailing list - it's already being used by many kernel trees
dont take this as "i love patchwork" ... ive never actually used it, but if it's gaining traction in major projects like the kernel, then having u-boot be the same is one less system for developers/contributors to have to be familiar with ... -mike
On Apr 2, 2009, at 7:44 AM, Mike Frysinger wrote:
On Thursday 02 April 2009 08:32:00 Detlev Zundel wrote:
not so long ago there was some custom thingy that was running on the u-boot website that'd automatically grab patches from the mailing list and try to file them away so they wouldnt get lost. but i cant seem to find it any more. is it gone ?
No, it is not gone, it only starts to bitrot :(
It also never by itself grabbed patches, but the idea was to post the patches to its own email account which in turn sent acknowledgements to the mailinglist _including_ a unique tracking number which was needed for automatic handling of follow-up mail.
Unfortunately the original implementor is not available anymore and we currently do not see how to finish the missing bits, especially the automatic handling of the status of patches.
If someone on this list with (solid) Perl knowledge volunteers to pick up the strings, let me know offlist.
thanks, that was the site i was looking for
maybe the lack of automation is a problem ? having a completely custom system is also a problem ...
would patchwork satisfy the same tracking needs ? benefits there are:
- automation
- someone else does the work of developing it
- all discussion stays tied to mailing list
- it's already being used by many kernel trees
dont take this as "i love patchwork" ... ive never actually used it, but if it's gaining traction in major projects like the kernel, then having u-boot be the same is one less system for developers/contributors to have to be familiar with ...
I would suggest patchworks as well just because there are those of us already using it w/the kernel community and having a similar work flow for u-boot is always nice :)
If desired we can ask the ozlab.org guys to host a u-boot patchwork if its something we want to try out.
- k
Mike Frysinger wrote:
On Thursday 02 April 2009 08:32:00 Detlev Zundel wrote:
not so long ago there was some custom thingy that was running on the u-boot website that'd automatically grab patches from the mailing list and try to file them away so they wouldnt get lost. but i cant seem to find it any more. is it gone ?
No, it is not gone, it only starts to bitrot :(
It also never by itself grabbed patches, but the idea was to post the patches to its own email account which in turn sent acknowledgements to the mailinglist _including_ a unique tracking number which was needed for automatic handling of follow-up mail.
Unfortunately the original implementor is not available anymore and we currently do not see how to finish the missing bits, especially the automatic handling of the status of patches.
If someone on this list with (solid) Perl knowledge volunteers to pick up the strings, let me know offlist.
I prefer python in my old age. :-P http://www.ozonehouse.com/mark/blog/code/PeriodicTable.html http://steve.yegge.googlepages.com/ancient-languages-perl
thanks, that was the site i was looking for
maybe the lack of automation is a problem ? having a completely custom system is also a problem ...
would patchwork satisfy the same tracking needs ? benefits there are:
- automation
- someone else does the work of developing it
- all discussion stays tied to mailing list
- it's already being used by many kernel trees
dont take this as "i love patchwork" ... ive never actually used it, but if it's gaining traction in major projects like the kernel, then having u-boot be the same is one less system for developers/contributors to have to be familiar with ... -mike
I also have looked at patchwork and thought it had to be better than our current (lack of a) system. I'm in awe of Wolfgang's organizational ability to track patches and am thankful libfdt is a calm backwater compared to the other subrepos.
Jean-Christophe did an experimental install of Patchwork (notification via non-list email with a subject line "Patchwork for U-Boot", looks like sent to custodians). I tried to register and failed, did not go further. Hmmm, tried again, failed again: ---------------------------------------------------------------------- Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log. ----------------------------------------------------------------------
How about looking at installing patchwork on denx.de? Was it evaluated and found lacking? At least you will be starting with non-broken perl. ;-)
gvb
Jerry Van Baren wrote:
Mike Frysinger wrote:
On Thursday 02 April 2009 08:32:00 Detlev Zundel wrote:
not so long ago there was some custom thingy that was running on the u-boot website that'd automatically grab patches from the mailing list and try to file them away so they wouldnt get lost. but i cant seem to find it any more. is it gone ?
No, it is not gone, it only starts to bitrot :(
It also never by itself grabbed patches, but the idea was to post the patches to its own email account which in turn sent acknowledgements to the mailinglist _including_ a unique tracking number which was needed for automatic handling of follow-up mail.
Unfortunately the original implementor is not available anymore and we currently do not see how to finish the missing bits, especially the automatic handling of the status of patches.
If someone on this list with (solid) Perl knowledge volunteers to pick up the strings, let me know offlist.
[snip]
How about looking at installing patchwork on denx.de? Was it evaluated and found lacking? At least you will be starting with non-broken perl. ;-)
http://ozlabs.org/git?p=patchwork;a=summary http://ozlabs.org/~jk/projects/patchwork/
Looks like patchwork is non-broken *python* (not perl) and uses Django as well. Mod patchwork +1. -------------------------------------------------------------------------- Patchwork is free software, and is available from the patchwork website. Patchwork is built on the django web framework. Patchwork includes the django-registration application. Icons from the Sweetie icon set. --------------------------------------------------------------------------
Easily impressed, gvb
participants (4)
-
Detlev Zundel -
Jerry Van Baren -
Kumar Gala -
Mike Frysinger