From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] avr32 patches vs. x86 breakage
Date: Fri, 21 Mar 2008 09:18:20 +0100 [thread overview]
Message-ID: <873aqk32yb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1206086506.2562.64.camel@nigel-x60> (Nigel Kukard's message of "Fri\, 21 Mar 2008 08\:01\:46 +0000")
>>>>> "Nigel" == Nigel Kukard <nkukard@lbsd.net> writes:
Hi,
Nigel> The other problem is getting some patches to get fixed when a problem is
Nigel> found ... not all of us are familiar with every single arch or even
Nigel> assembly in some cases, let alone arch specific assembly.
Nigel> I think a split would be a good idea, also maybe make it
Nigel> easier to debug issues.
Or atleast only let the people using that particular arch worry about
it ;)
>> - package-version-*.patch for generic stuff
>> - arch-package-version-*.patch for arch specific stuff
>>
>> What do you think?
Nigel> What about patch order? and patch order when there is generic stuff and
Nigel> arch specific?
My (possibly too simplistic) view on things is to first apply the
generic patches, and then the arch specific ones.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-03-21 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 6:00 [Buildroot] avr32 patches vs. x86 breakage Nigel Kukard
2008-03-21 7:45 ` Peter Korsgaard
[not found] ` <1206086506.2562.64.camel@nigel-x60>
2008-03-21 8:18 ` Peter Korsgaard [this message]
2008-03-21 8:38 ` Nigel Kukard
2008-03-21 8:52 ` Bernhard Fischer
2008-03-21 9:12 ` Nigel Kukard
2008-03-21 9:30 ` Peter Korsgaard
2008-03-25 8:55 ` Ulf Samuelsson
[not found] ` <87hcf01m0r.fsf@macbook.be.48ers.dk>
2008-03-21 9:32 ` Peter Korsgaard
2008-03-21 11:36 ` John Voltz
2008-03-21 12:11 ` Bernhard Fischer
2008-03-21 12:47 ` John Voltz
2008-03-25 8:50 ` Ulf Samuelsson
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=873aqk32yb.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.