From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 6 Feb 2014 16:50:27 +0100 Subject: [Buildroot] [PATCH 1/2] Qt5: update to 5.2.1 In-Reply-To: References: <20140206162743.2ae6f50e@skate> Message-ID: <20140206165027.64911e84@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Peter Kuemmel, On Thu, 6 Feb 2014 16:44:28 +0100 (CET), Peter Kuemmel wrote: > > As explained in the documentation, could you use "git send-email" to > > Sorry, I thought using send-email is just optional. It is in some sense optional, if you do send patches "the right way". But the easiest solution to send them "the right way" is to use git send-email. > So someone else interested should put it into the queue, > but don't use my signed-off patches. Unfortunately, this often doesn't work: once someone sends patches, there are review comments, and the submitter often has to make a few changes, and resubmit. So if someone else picks up your patches, he will have to do this work, while as the original author of the patches, it would be much easier if you did this work. Those contributions are very useful to Buildroot, so it would very appreciated if you could go through the contribution process completely. I know it takes a bit of time, but it is a necessary process to ensure that the quality of patches merged is up to the standards the community has defined. Thanks a lot! Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com