From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] HUGE patch for buildroot
Date: Sun, 10 Feb 2008 18:49:41 +0200 (EET) [thread overview]
Message-ID: <45445.127.0.0.1.1202662181.squirrel@localhost> (raw)
In-Reply-To: <46a136670802091828v558e5d50n131cc9076605bd7c@mail.gmail.com>
Hi John,
Of course please post your patch. Even if the patch too huge somebody will split it.
Regards,
Ivan
> Hello,
>
> I'm wondering if the buildroot maintainers frequent this list, and if
> so, how do you feel about receiving a humongous patch for it? I've
> been working on bugfixes for well over a week now and I believe it's
> going to be a huge patch. It would take me weeks more to break it into
> individual patches. So far I've fixed a bunch of incorrect package
> install arguments that cause problems with pkgconfig and libtool
> resulting in build failures. I've added the X.org fonts and some other
> missing X.org packages, icu, fltk, webkit, midori, ipkg, updated
> cairo, pango, gtk, and glib to the latest versions. I also merged the
> current branch of the Atmel AVR32 buildroot architecture for that CPU.
> Is there any interest in it, or should I just keep it to myself?
>
> Kind regards,
> John Voltz
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2008-02-10 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 2:28 [Buildroot] HUGE patch for buildroot John Voltz
2008-02-10 3:04 ` Ormund Williams
2008-02-10 16:49 ` Ivan Kuten [this message]
2008-02-10 23:23 ` Hamish Moffatt
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=45445.127.0.0.1.1202662181.squirrel@localhost \
--to=ivan.kuten@promwad.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