From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0005234]: Selecting MTD utils from git doesn't give you the HEAD
Date: Tue, 7 Oct 2008 16:19:41 +1100 [thread overview]
Message-ID: <20081007051941.GD5127@cloud.net.au> (raw)
In-Reply-To: <532a9ee2ed7a6e52612f1f2e0680f030@bugs.uclibc.org>
On Fri, Oct 03, 2008 at 09:42:04AM -0700, bugs at busybox.net wrote:
> #############################################################
> -MTD_VERSION:=fcb52ccc99679460640386c297023f852b108f68
> +MTD_VERSION:=HEAD
Not a good idea. I did this originally.
Problem is that it'll download head once, but nothing will cause it to
download head again (unless you remove the .tar.gz from the sources
directory). AND you don't know what version you have either if you want
to rebuild later.
Also, the patches won't necessarily apply to a later version.
A configuration option would be an improvement though it doesn't solve
the patch problem.
I think it really needs manual intervention, which is how it came to be
how it is now.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-10-07 5:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 16:42 [Buildroot] [buildroot 0005234]: Selecting MTD utils from git doesn't give you the HEAD bugs at busybox.net
2008-10-07 5:19 ` Hamish Moffatt [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-08 0:54 bugs at busybox.net
2008-10-08 0:10 bugs at busybox.net
2008-10-07 13:46 bugs at busybox.net
2008-10-07 13:36 bugs at busybox.net
2008-10-07 13:20 bugs at busybox.net
2008-10-07 13:17 bugs at busybox.net
2008-10-07 7:07 bugs at busybox.net
2008-10-07 5:00 bugs at busybox.net
2008-10-03 23:49 bugs at busybox.net
2008-10-03 23:47 bugs at busybox.net
2008-10-03 17:01 bugs at busybox.net
2008-10-03 16:40 bugs at busybox.net
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=20081007051941.GD5127@cloud.net.au \
--to=hamish@cloud.net.au \
--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