[Buildroot] Preferred procedure for submitting patches?

[Buildroot] Preferred procedure for submitting patches?

[Alex Stewart]

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

[Buildroot] Preferred procedure for submitting patches?

[Bernhard Fischer]

On Thu, Feb 15, 2007 at 02:09:29PM -0800, Alex Stewart wrote:
>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?

Given that there were more than 250 open buildroot bugs in november and
we already were < 75 last time i looked, yes, i'm slowly going through
the bugs entered there.

Some categories of reports i cannot really deal with (cannot emulate the
arch the bug is reported against and noone is able/willing to provide a
kernel .config that i can use qith e.g. qemu).
Other categories (external toolchain, ancient versions that have working
current counterparts) i don't care about, personally.

>
>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?

Submitting patches to the bugtracker is nice, provided that it comes
along a good description of the problem/feature it is solving and/or has
a way to reproduce the failure while i can actually _test_ that the
outcome works for an emulated target.
Sometimes i ask that patches are also sent to the list. Patches that are
solely sent to the list are sometimes lost if noone immediately "takes"
them, of course.

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 ;)

HTH. Cheers,

[Buildroot] Preferred procedure for submitting patches?

[Alex Stewart]

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