On 06/11/2019 21:41, Adrian Bunk wrote:
1. Patch review
Merge requests work well when there is one maintainer who reviews
everything. For not regressing on the current level of review before
something hits master, merging a merge request into master-next
should then result in patch review
On Wed, Nov 06, 2019 at 04:01:03PM +, Paul Barker wrote:
>...
> At the risk of bikeshedding I'd like to get some feedback on these ideas at
> this stage. Have I missed any advantages/disadvantages?
>...
Three comments from me:
1. Patch review
Merge requests work well when there is one
Hey folks,
We had some initial discussion at OEDEM about the patch submission process and
how repositories are hosted (see
https://docs.google.com/document/d/1Qm1mJ6xLozWW9NgBnokue7TmhwgFP8b2HR8TUlaQwNs/edit#heading=h.o4qtddy8bh9i).
Patch submission via mailing list still has some key features