> Pushing patchwork patches into a git would be trivial for me to do (ie after > some passed initial test as patches)
It seems promising, at least, we can give it a try to see if it at least addresses one of the issue Vincent pointed out below. > If the community likes this, then let me know and we could figure out details > (branch? Potentially create new branch for each patchwork?) > > BTW: Atlassian git (Bitbucket server) allows permission per branch - would be > easy to lock main branch(es) to maintainers without locking everything. Attractive, but would like to see the patchwork/git interaction in action first. Just my two cents. Cheers, Kei > > - Martin > > On Tue, Jan 19, 2016 at 3:36 PM, Vincent JARDIN <[email protected]> > wrote: > On 19/01/2016 20:59, Kei Nohguchi wrote: > the original reason, or pain, with the patchwork? > > benefit of patchwork: simple > issues of patchwork: very limited tracking and very light integration with > git (git review is missing). > > > _______________________________________________ > Quagga-dev mailing list > [email protected] > https://lists.quagga.net/mailman/listinfo/quagga-dev > > _______________________________________________ > Quagga-dev mailing list > [email protected] > https://lists.quagga.net/mailman/listinfo/quagga-dev _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
