From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Zick Date: Sat, 7 Jun 2014 09:30:54 -0500 Subject: [Buildroot] Patch: qt5webkitexamples In-Reply-To: <1402138061.2503.YahooMailNeo@web172304.mail.ir2.yahoo.com> References: <1402067773.64897.YahooMailNeo@web172303.mail.ir2.yahoo.com> <20140607122338.33ab44ce@free-electrons.com> <1402138061.2503.YahooMailNeo@web172304.mail.ir2.yahoo.com> Message-ID: <20140607093054.296dceda@core2quad.morethan.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Sat, 7 Jun 2014 11:47:41 +0100 (BST) Massimo Callegari wrote: > Hello Thomas, > then I clearly haven't read the whole guidelines in the BR manual. > Apologies for that. > > I am totally aware that the patch system this project adopted is > working since years. Mine was just a suggestion since I work on a > daily basis with GitHub and I find it simply splendid for code > review. Maybe it's just my impression but the flow "fork -> patch -> > pull request" sounds easier than manual git commands where you have > to remember the email address of a mailing list (thus human > errors...) and where dozens of emails float around every day even to > users not interested in a particular topic. In my opinion a mailing > list should be used only to discuss bugs, ideas and help users. In > the current way, users emails risk to get lost into a ton of [PATCH] > emails. Maybe a ML dedicated to patches could help ? > This mailing list uses dedicated tags in the subject line. Just set your e-mail client to filter by the tag into different sub-directories. Then you don't have to look in (for example) BuildRoot/BR_Patch directory unless you want to. ;) Same with commit, bug and autobuilder messages. No, I am not trying to be stubborn, it is just a system that the developers are comfortable with. I find (I am a 99.9% read-only ML member) a bit of e-mail filtering helps a lot in dealing with the flood of information here. ;) Mike