From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] problem building openswan using svn-buildroot
Date: Tue, 24 Feb 2009 23:30:46 +0100 [thread overview]
Message-ID: <87skm3zcvd.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <93F12DDAEC3E4BBFBAA4E030667F5EDD@aeglos> (Ulf Samuelsson's message of "Tue\, 24 Feb 2009 22\:42\:46 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Hi,
>> Well - It's HUGE (>7M), but OK, I'll mark it as BROKEN and remove if
>> after the 2009.05 release unless someone steps up to fix it. I'll also
>> remove the kernel patches as we remove old kernel versions.
Ulf> If you feel that the stuff should not be in the svn, then
Ulf> make the patches loadable and store the patches in the mirror.
What will that change if it's broken?
Ulf> As pointed out to you earlier, buildroot users are using
Ulf> linux-2.6.22 and later so there is no reason to remove things
Ulf> which is active use. Again, it makes sense to move the patches
Ulf> to the mirror, but yuu are the only one to have write acdess as
Ulf> far as I know.
Active openswan users? How come we haven't seen any bugreports or
patches since 2007 then?
As said earlier, I think it's absolutely critical to trim the package
versions between releases, otherwise we'll never be able to get any
significant testing coverage.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-24 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 1:21 [Buildroot] problem building openswan using svn-buildroot Robert Urban
2009-02-22 7:23 ` Peter Korsgaard
[not found] ` <49A17E91.7060104@unix-beratung.de>
2009-02-22 18:11 ` Peter Korsgaard
2009-02-23 10:28 ` Steffen Schulz
2009-02-23 11:14 ` Peter Korsgaard
2009-02-23 14:33 ` Steffen Schulz
2009-02-23 14:44 ` Peter Korsgaard
2009-02-24 6:14 ` Ulf Samuelsson
2009-02-24 7:20 ` Peter Korsgaard
2009-02-24 21:42 ` Ulf Samuelsson
2009-02-24 22:30 ` Peter Korsgaard [this message]
2009-02-25 5:40 ` 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=87skm3zcvd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox