[Replicant] Patch tracking, Was: i9305: Add support for rt2500usb wifi devices

[doak]

Hello,

only reading the Wiki about 'patchwork', it seems to be interesting and just enough to get an overview of provided patches.

OT:
I was just thinking "why not use own hosted GitLab instance" which would imho contain everything which we need but some forum. But then I have found the quite fresh discussion which was summarised very detailed by Wolfgang here:
  https://redmine.replicant.us/projects/replicant/activity?from=2017-08-29
Though, I would like to have the merge request workflow (and still have the feeling that this widely known "concept" would help to get more attention), I agree that this is probably not the most complicated concept you need to get used to to be able to develop for Replicant.
Not forgetting the issues regarding performance with /a lot/ of /big/ repositories (Wolfgang linked it) and perhaps SaS issues.


Best regards,
doak



On 23 March 2018 21:48:00 CET, "Joonas Kylmälä" <joonas.kylmala at iki.fi> wrote:
>Hi!
>
>Denis 'GNUtoo' Carikli:
>> Would some tool like patchwork be a good idea to track the patches
>> status?
>
>I like the idea. I have found patchwork very useful when one needs to
>download patches sent to mailing list before joining the list, or if
>you
>are developing on different machine where you have your emails.
>
>Should we host ourselves or do you know somebody who has patchwork
>software already installed and we could join the instance?
>
>Joonas
>_______________________________________________
>Replicant mailing list
>Replicant at osuosl.org
>https://lists.osuosl.org/mailman/listinfo/replicant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 845 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20180324/9072ed98/attachment.asc>