All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Stewart <alex@foogod.com>
To: buildroot@busybox.net
Subject: [Buildroot] Preferred procedure for submitting patches?
Date: Thu, 15 Feb 2007 14:09:29 -0800	[thread overview]
Message-ID: <20070215220929.GA1805@foogod.com> (raw)

Hi all..

I was wondering what the preferred method for submitting patches to buildroot
is?  I've recently submitted several patches through the bug reporting system,
but now I'm noticing that there seem to be other patches in the bug system from
several months ago (bug 1094, for example, which I just noticed is basically a
duplicate of something I just submitted, that somebody else provided a fix for
last November) that still apparently haven't been applied to the current
sources, so now I'm beginning to wonder whether anybody's really paying
attention to the bug system?

Is there some other method I should be using to submit patches to make sure
they make it into the distribution in a timely fashion?

-alex

             reply	other threads:[~2007-02-15 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 22:09 Alex Stewart [this message]
2007-02-16  8:30 ` [Buildroot] Preferred procedure for submitting patches? Bernhard Fischer
2007-02-16 19:16   ` Alex Stewart

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=20070215220929.GA1805@foogod.com \
    --to=alex@foogod.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 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.