From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] legacy sources in svn
Date: Sat, 29 Mar 2008 13:29:17 +0100 [thread overview]
Message-ID: <87prtdaf36.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <87a5b0800803290508t3b1bd407n1eb2e2c76c2a803a@mail.gmail.com> (Will Newton's message of "Sat\, 29 Mar 2008 12\:08\:19 +0000")
>>>>> "Will" == Will Newton <will.newton@gmail.com> writes:
Hi,
>> Exactly, feel free to remove them.
Will> I have some concerns about this. People may want to keep stable
Will> toolchains to avoid bugs in newer versions or for QA purposes.
Will> Removing working configurations in the name of "tidying up" sounds
Will> like a bad idea to me.
The question was about removing old patches that aren't used (the
versions cannot be selected) anymore.
Regarding updating versions - We do that all the time (and have to do
so as bugs are found in old versions or they simply no longer
available upstream). If you want to keep a stable environment, you
should simply not update your buildroot snapshot.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2008-03-29 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 21:06 [Buildroot] legacy sources in svn Nigel Kukard
2008-03-28 21:14 ` Peter Korsgaard
2008-03-29 12:08 ` Will Newton
2008-03-29 12:23 ` Nigel Kukard
2008-03-29 12:29 ` Peter Korsgaard [this message]
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=87prtdaf36.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