From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] Mac OS X status
Date: Tue, 27 Feb 2007 23:17:48 +0200 [thread overview]
Message-ID: <45E49FFC.4020404@cs.helsinki.fi> (raw)
In-Reply-To: <b15982770702271213l2c59fb27nc2050d97831ef62a@mail.gmail.com>
...and should patches be put exclusively to the bug tracker to be noted
at all? A discouraging fact is that the only OS X patch I found in the
tracker took half a year to get any response. Trying to keep out-of-tree
patches in sync with SVN changes for that long can be a pain. In the
meantime, I fixed the fakeroot issue and that stuff is already available
in fakeroot 1.6.2 from your friendly neighbourhood debian site.
-- Heikki Lindholm
David Smoot kirjoitti:
> So who / whom are the powers that make that decision and what is their
> opinion on merging in changes to support buildroot on Mac OS X?
> David
>
> On 2/25/07, * Allan Clark* <allanc@chickenandporn.com
> <mailto:allanc@chickenandporn.com>> wrote:
>
> <snip>
>
> I've contributed to this in the past, others have, this would need
> some assurance that the parts for buildroot on MacOSX would have a
> chance of merging to baseline, or there will probably be an annual
> "hey, I have an idea, buildroot on MacOSX" attempt. If the changes go
> to baseline, then the issue becomes maintenance, not re-invention.
>
> Allan
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2007-02-27 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 11:38 [Buildroot] Mac OS X status Heikki Lindholm
2007-02-26 1:20 ` David Smoot
2007-02-26 1:26 ` Allan Clark
2007-02-27 20:13 ` David Smoot
2007-02-27 21:17 ` Heikki Lindholm [this message]
2007-03-08 16:43 ` Bernhard Fischer
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=45E49FFC.4020404@cs.helsinki.fi \
--to=holindho@cs.helsinki.fi \
--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