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: Fri, 16 Feb 2007 11:16:49 -0800	[thread overview]
Message-ID: <20070216191649.GA13041@foogod.com> (raw)
In-Reply-To: <20070216083019.GA27053@aon.at>

On Fri, Feb 16, 2007 at 09:30:19AM +0100, Bernhard Fischer wrote:
> The timely bit could be solved by paying somebody. Ask Erik or whomever
> if you want this. I'm just a volunteer, ultimately, so i'm not going to
> adhere to anybody putting any constraints on me in this respect ;)

Please don't take my message the wrong way.  I wasn't attempting to demand a
timely response ("fix my bugs now! waah!") or anything, I'm quite familiar with
the nature of open source projects sometimes.  I just wanted to make sure I was
sending my submissions to the right place, which it sounds like I have been..

It's just that I was seeing svn commits happening all the time, but they didn't
seem to be related to any of the existing patches I see that have been
submitted through the bug system, so I was wondering if they were coming
through some other channel instead.

(Please also note, I wasn't talking about bug reports that people have to track
down and isolate and figure out a fix for and then code up a solution.  I can
understand that that would take some effort and might not happen at all.  I'm
talking about issues where a patch already exists and has been submitted, and
just needs to be applied to the svn repo.  I've tried to make all of my bug
reports of this form, to minimize the work for maintainers)

As for people not having enough time to handle all of the bugs, I would be
willing to volunteer some of my time to this as well if it would help, but
unfortunately I don't have svn commit access, so when it comes to applying
patches that already exist, I can't help much there...

-alex

      reply	other threads:[~2007-02-16 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 22:09 [Buildroot] Preferred procedure for submitting patches? Alex Stewart
2007-02-16  8:30 ` Bernhard Fischer
2007-02-16 19:16   ` Alex Stewart [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=20070216191649.GA13041@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.