On Tue, 15 Oct 2019 19:37:04 +0300 Laurent Pinchart <laurent.pinch...@ideasonboard.com> wrote:
> But how far could we push this reasoning ? I've worked for a company > whose corporate policy was that all source code had to be stored in SVN, > not exception. I didn't reach the community to move kernel development > away from git. I've also worked with people whose corporate policy was > that they had to do Linux kernel development on Windows, without using > any virtual machine. There are all kind of crazy corporate policies, and > if we don't push the pain it inflicts on all of us back to the people > who enact those crazy policies, we'll always lose. I understand your sentiment. But most of your examples are one-off "crazy corporate policies". The "sucky email server" and "you must use this sucky email server" is rather standard. Not saying that we don't want to pressure them to change, but I'm hearing from people (like Dave Miller), that new developers are moving away from email for development. I thought part of this thread was talking about having other ways besides email to submit a patch. Something that can help people correctly send a patch (at least their formatting) by making sure they fill out the proper fields and have a tool that helps them do so. I brought up the corporate email servers just as an example of having this help out there too. I plan on continuing to develop mostly in email (I still send my patch series via quilt!). But I'm not going to enforce everyone to continue to use email if we can come up with a better way. I also want to make sure that whatever we do come up with will still support email. -- Steve _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
