From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/u-boot
Date: Wed, 23 Apr 2008 20:37:11 +0200 [thread overview]
Message-ID: <20080423183710.GD10167@mx.loc> (raw)
In-Reply-To: <018c01c8a56d$beab6120$020514ac@atmel.com>
On Wed, Apr 23, 2008 at 07:39:38PM +0200, Ulf Samuelsson wrote:
>
>
>> On Wed, Apr 23, 2008 at 06:22:46PM +0200, Ulf Samuelsson wrote:
>>>
>>>> Hmmm I have never seen patch.$ARCH in buildroot.
>>>>
>>>> It's usually -$ARCH.patch like toolchain/kernel-headers
>>>> package/qtopia4 and others.
>>>
>>>
>>>If you patch with "*.patch", then *all* architecture dependent patches will be applied
>>>if you use "-$ARCH.patch"
>>>
>>>You want to apply
>>>* architecture independent patches
>>>* architecture dependent patches pertaining to your architecture.
>>>
>>>so ".patch.$ARCH" is much cleaner
>>
>> The concept of per-arch patches is broken per se. You're better off to
>> fix or drop the dysfunctional patches.
>
>
>The per-arch patch is low maintenance, while your idea is high maintenance.
We already had that argument, so let me just repeat that you have to
fixup your port anyway, sooner or later. 'nuff said
next prev parent reply other threads:[~2008-04-23 18:37 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 14:52 [Buildroot] svn commit: trunk/buildroot/target/u-boot jacmet at uclibc.org
2008-04-23 14:59 ` Thiago A. Corrêa
2008-04-23 15:20 ` Peter Korsgaard
2008-04-23 16:22 ` Ulf Samuelsson
2008-04-23 17:35 ` Bernhard Fischer
2008-04-23 17:39 ` Ulf Samuelsson
2008-04-23 18:37 ` Bernhard Fischer [this message]
2008-04-23 18:29 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 15:19 jacmet at uclibc.org
2009-02-10 15:19 jacmet at uclibc.org
2009-02-10 15:19 jacmet at uclibc.org
2009-02-07 6:57 jacmet at uclibc.org
2009-02-04 23:15 jacmet at uclibc.org
2009-01-26 14:49 jacmet at uclibc.org
2009-01-26 14:49 jacmet at uclibc.org
2009-01-26 14:04 jacmet at uclibc.org
2009-01-26 11:46 ulf at uclibc.org
2009-01-22 18:46 ulf at uclibc.org
2009-01-22 10:15 jacmet at uclibc.org
2009-01-21 15:49 jacmet at uclibc.org
2009-01-20 8:11 ulf at uclibc.org
2009-01-11 21:39 ulf at uclibc.org
2009-01-24 8:21 ` Peter Korsgaard
2009-01-24 10:55 ` Ulf Samuelsson
2009-01-24 11:43 ` Peter Korsgaard
2009-01-24 15:27 ` Dan Lyke
2009-01-08 14:58 jacmet at uclibc.org
2009-01-08 14:58 jacmet at uclibc.org
2009-01-06 14:16 ulf at uclibc.org
2009-01-06 14:26 ` Peter Korsgaard
2009-01-06 16:06 ` Ulf Samuelsson
2009-01-05 16:16 jacmet at uclibc.org
2009-01-05 16:12 jacmet at uclibc.org
2009-01-05 18:12 ` Ulf Samuelsson
2009-01-05 18:16 ` Ulf Samuelsson
2009-01-05 20:14 ` Peter Korsgaard
2009-01-05 20:12 ` Peter Korsgaard
2009-01-06 12:50 ` Ulf Samuelsson
2009-01-06 12:59 ` Peter Korsgaard
2009-01-05 15:52 jacmet at uclibc.org
2009-01-03 15:03 nkukard at uclibc.org
2009-01-03 0:02 ulf at uclibc.org
2009-01-03 20:46 ` Peter Korsgaard
2009-01-03 20:18 ` Ulf Samuelsson
2009-01-03 0:00 ulf at uclibc.org
2009-01-03 20:28 ` Peter Korsgaard
2009-01-03 20:37 ` Ulf Samuelsson
2008-08-20 20:04 jacmet at uclibc.org
2008-08-20 20:04 jacmet at uclibc.org
2008-08-20 20:04 jacmet at uclibc.org
2008-07-08 10:53 jacmet at uclibc.org
2008-07-04 22:18 ulf at uclibc.org
2008-07-07 13:27 ` Peter Korsgaard
2008-06-17 8:04 jacmet at uclibc.org
2008-06-13 13:46 jacmet at uclibc.org
2008-06-12 7:27 jacmet at uclibc.org
2008-06-11 13:07 jacmet at uclibc.org
2008-06-12 5:14 ` Hamish Moffatt
2008-06-12 7:28 ` Peter Korsgaard
2008-04-23 14:52 jacmet at uclibc.org
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 16:09 ` Ulf Samuelsson
2008-04-23 18:05 ` Peter Korsgaard
2008-04-23 18:35 ` Ulf Samuelsson
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 10:30 jacmet at uclibc.org
2008-04-09 7:02 jacmet at uclibc.org
2008-04-09 7:02 jacmet at uclibc.org
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=20080423183710.GD10167@mx.loc \
--to=rep.dot.nop@gmail.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