From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patch: qt5webkitexamples
Date: Sat, 7 Jun 2014 12:23:38 +0200 [thread overview]
Message-ID: <20140607122338.33ab44ce@free-electrons.com> (raw)
In-Reply-To: <1402067773.64897.YahooMailNeo@web172303.mail.ir2.yahoo.com>
Dear Massimo Callegari,
On Fri, 6 Jun 2014 16:16:13 +0100 (BST), Massimo Callegari wrote:
> Hi, attached a patch that adds the missing qt5 webkit examples module.
Thanks for your contribution! However, as Mike Zick said, and as
explained in the Buildroot manual, patches should be submitted inline.
The 'git send-email' tool does that for you.
> One thing though. Have you ever considered migrating to GitHub ?
> Submitting patches via email is, in my opinion, extremely inefficient and can lead to human errors.
Which human errors? If you use 'git send-email', there is no problem at
all, and sending patches just requires one command.
Submitting patches on a mailing list allows people to easily review
them, discuss comments. Buildroot is by far not the only community to
do this. Other major communities in the embedded Linux space do the
same: the kernel, U-Boot, Barebox and others.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-07 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 15:16 [Buildroot] Patch: qt5webkitexamples Massimo Callegari
2014-06-06 16:21 ` Mike Zick
2014-06-07 10:23 ` Thomas Petazzoni [this message]
2014-06-07 10:47 ` Massimo Callegari
2014-06-07 14:30 ` Mike Zick
2014-06-07 16:48 ` Thomas Petazzoni
2014-06-09 21:12 ` Peter Korsgaard
2015-03-05 11:27 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140607122338.33ab44ce@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox