All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] commiting patches
Date: Thu, 30 Dec 2010 21:58:41 +0100	[thread overview]
Message-ID: <87y677gepq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201012301918.42811.yann.morin.1998@anciens.enib.fr> (Yann E. MORIN's message of "Thu, 30 Dec 2010 19:18:42 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@anciens.enib.fr> writes:

Hi,

 >> I was wondering for a while, what are the criterias for patches to
 >> be applied to buildroot.  Some of them seem to get applied right
 >> away, others were sent in a month or two ago and don't. I understand
 >> that some probably will never get applied, but will there be a
 >> "sorry dude, but..." email?  Just curious how this is handled.

 Yann> Well, I won't speak for Peter, or any other participant, but
 Yann> here's what I believe is the proper way to act:

Thanks for this extended guide! I do completely agree with it. Minor
issues such as style / format DO matter for what patches I look at
first.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-12-30 20:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 12:30 [Buildroot] commiting patches Heiko Zuerker
2010-12-30 18:18 ` Yann E. MORIN
2010-12-30 20:58   ` Peter Korsgaard [this message]
2010-12-30 20:54 ` Peter Korsgaard
2010-12-30 21:04   ` Daniel Nyström
2010-12-30 21:24     ` Sam Ravnborg
2010-12-30 22:07     ` Peter Korsgaard
2010-12-30 22:22       ` Daniel Nyström
2010-12-30 22:25         ` Peter Korsgaard
2010-12-30 22:24       ` Heiko Zuerker
2010-12-30 22:30         ` Peter Korsgaard
2010-12-30 22:39           ` Bryan Hundven
2010-12-30 21:38   ` Heiko Zuerker
2011-01-03  8:08   ` Thomas Petazzoni
2011-01-03  8:32     ` Peter Korsgaard
2011-01-03 13:47       ` Heiko Zuerker

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=87y677gepq.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.