Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Patch: qt5webkitexamples
Date: Sat, 7 Jun 2014 09:30:54 -0500	[thread overview]
Message-ID: <20140607093054.296dceda@core2quad.morethan.org> (raw)
In-Reply-To: <1402138061.2503.YahooMailNeo@web172304.mail.ir2.yahoo.com>

On Sat, 7 Jun 2014 11:47:41 +0100 (BST)
Massimo Callegari <massimocallegari@yahoo.it> 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

  reply	other threads:[~2014-06-07 14:30 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
2014-06-07 10:47   ` Massimo Callegari
2014-06-07 14:30     ` Mike Zick [this message]
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=20140607093054.296dceda@core2quad.morethan.org \
    --to=minimod@morethan.org \
    --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