[elbe-devel] Patch/PRs management

torben.hohn at linutronix.de torben.hohn at linutronix.de
Fri Jan 24 20:29:53 CET 2020


On Fri, Jan 24, 2020 at 10:03:28AM +0100, Yegor Yefremov wrote:
> Dear ELBE maintainers,
> 
> are there any plans to either introduce patchwork [1] or move
> completely to GitHub in order to better track the patches and their
> state?

Its not very likely, that we will setup our own patchwork.
But maybe we can make some patchwork subscibe to our list.

I will ask around.

> 
> I would go for the GitHub solution. The author of the PR can always
> see whether his PR got conflicts. Another goodie is TravisCI support.
> We could add at least Python linting and codespell tests. See how RIOT
> OS community handles this [2] and [3]. Unittest can also be developed.

As for pull request or other tracking per github, this is not compatible
with out workflows. Linutronix Workflows are based on E-Mail.

I am currently on a train with crappy Internet, and i can work just
fine.


> 
> What do you think?
> 
> [1] https://patchwork.ozlabs.org/
> [2] https://github.com/RIOT-OS/RIOT/blob/master/dist/tools/codespell/check.sh
> [3] https://github.com/RIOT-OS/RIOT/tree/master/dist/tools/flake8
> 
> Regards,
> Yegor
> 
> _______________________________________________
> elbe-devel mailing list
> elbe-devel at linutronix.de
> https://lists.linutronix.de/mailman/listinfo/elbe-devel



More information about the elbe-devel mailing list