From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] avr32 patches vs. x86 breakage
Date: Fri, 21 Mar 2008 08:38:47 +0000 [thread overview]
Message-ID: <1206088727.2562.72.camel@nigel-x60> (raw)
In-Reply-To: <873aqk32yb.fsf@macbook.be.48ers.dk>
Hi,
> >> - 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.
yea, generic first I think aswell.
few more thoughts...
these would be in for instance toolchain/gcc/
1.
version/*.patch - generic
version/arch/*.patch - arch specific
2.
version/*.patch
arch-version/*.patch
3.
version-*.patch
arch-version-*.patch
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080321/9ad75c06/attachment.pgp
next prev parent reply other threads:[~2008-03-21 8:38 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
2008-03-21 8:38 ` Nigel Kukard [this message]
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=1206088727.2562.72.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--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