From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] legacy sources in svn
Date: Fri, 28 Mar 2008 22:14:52 +0100 [thread overview]
Message-ID: <87k5jmft4j.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1206738394.3224.82.camel@nigel-x60> (Nigel Kukard's message of "Fri\, 28 Mar 2008 21\:06\:34 +0000")
>>>>> "Nigel" == Nigel Kukard <nkukard@lbsd.net> writes:
Nigel> Is there a reason for example that there are removed gcc
Nigel> versions still in toolchain/gcc/x.y.z ?
Nigel> Are they kept there incase someone needs to build an older version?
I think people simply forget to remove them when they remove the
Kconfig stuff - I have lately been cleaning up the uClibc patches that
weren't used any more.
Nigel> Surely they can get the old patches from svn? I mean, the
Nigel> versions are mostly removed from all Config.in and .mk files
Nigel> anyway?
Exactly, feel free to remove them.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-03-28 21:14 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 [this message]
2008-03-29 12:08 ` Will Newton
2008-03-29 12:23 ` Nigel Kukard
2008-03-29 12:29 ` Peter Korsgaard
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=87k5jmft4j.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