On 19 January 2018 at 13:57, Oleg Kokorin <ole2m...@mail.com> wrote: > I've got the points and re-sent the patch, but I'd like to add mine: > > by adding complexity instead of taking care of git and specifically > send-email command providing necessary portions you'd like to have in patch > in automated manner - you are decrising number of participants > significantly. >
Re-adding oe-core again. How can git know that you're the original author of the patch and didn't just copy/paste? How can git know that you've hacked a workaround, or backported a fix from upstream? I'm fine with a small barrier to contributions when it means that in five years time I'm not scratching my head at a patch with lost history, no comments, no ownership, no indication whether it's a workaround or should be sent upstream, wondering what it was meant to do. There are still plenty of patches like that in oe-core, where the history disappears into BitKeeper repositories that nobody has anymore. Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
