From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Sending Patches, Updates Etc.
Date: Tue, 03 Mar 2009 15:57:26 -0200 [thread overview]
Message-ID: <49AD6F86.5000708@zacarias.com.ar> (raw)
In-Reply-To: <D61182AC8012EA4EBC531B3AF23BE109769AC1@tranzeo-mail2.12stewart.tranzeo.com>
Darcy Watkins wrote:
> Hello,
>
> Someone please advise me regarding the preferred approach, guidelines,
> etc. to submitting changes, updates, etc. Many months back, I submitted
> a patch to mkcramfs and it never made it in. I'd like to resubmit it
> and other changes for consideration. Also, I have modified the
> menuconfig/config utility so that the "source" command's filespec uses
> 'glob' to handle wildcards, e.g. like...
>
> source "package/*/Config.in"
>
> ...and I have a few other ideas, I'd like to discuss in relation to
> this.
>
> Do I need to open a bug report first, then submit a patch?
>
> Has anyone considered setting up a patchwork web for buildroot, uclibc
> and busybox projects?
>
> Regards,
>
> Darcy
Hi.
https://bugs.busybox.net has the new tracker, i submit patches there
under the "buildroot" product. Some made it in, some are pending (dev
time, interest, my patches being cleaner, ...)
Regards.
prev parent reply other threads:[~2009-03-03 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 17:10 [Buildroot] Sending Patches, Updates Etc Darcy Watkins
2009-03-03 17:57 ` Gustavo Zacarias [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=49AD6F86.5000708@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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