Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about patches
Date: Thu, 7 Feb 2013 09:31:29 +0100	[thread overview]
Message-ID: <20130207093129.47baa875@skate> (raw)
In-Reply-To: <EE5E77B503DE9A478B63A89AAD2585EDB66A47@vpane.excalyptech.com>

Dear Przemyslaw Wrzos,

On Thu, 7 Feb 2013 11:47:35 +1100, Przemyslaw Wrzos wrote:
> Great, thanks for the heads up. The patch was more of an enhancement
> so there's no rush, just wanted to make sure it wouldn't get lost.

Nowadays, patches normally don't get lost: whenever a patch is sent to
the list, it is recorded by our "patchwork" and becomes listed at
http://patchwork.ozlabs.org/project/buildroot/list/. Then, it takes
some human action to either apply the patch, or remove it from this
list, or something. But at least all patches sent to the list are
recorded.

However, as you can see, the number of patches to be applied/considered
is quite large, so if your patch hasn't had much attention, it is not
bad after a week or two (as suggested by Arnout) to ask what is
happening.

> I had a quick look around the website but couldn't find a release
> schedule, merge windows, etc. If there's nothing like that right now
> it would probably be useful to help keep a track of what's going on
> for end developers who are not as closely involved with the project.

Hum, indeed. Will try to cook a patch for the manual about this.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2013-02-07  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  0:05 [Buildroot] Question about patches Przemyslaw Wrzos
2013-02-06  8:40 ` Stephan Hoffmann
2013-02-06 22:37 ` Yann E. MORIN
2013-02-07  0:47   ` Przemyslaw Wrzos
2013-02-07  8:08     ` Daniel Nyström
2013-02-07  8:31     ` Thomas Petazzoni [this message]

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=20130207093129.47baa875@skate \
    --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