From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Feature request - pull sources from repose
Date: Thu, 07 Jul 2011 19:22:09 +0200 [thread overview]
Message-ID: <87wrfuqa4e.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <5725744097739393062@unknownmsgid> (James Hanley's message of "Thu, 7 Jul 2011 10:06:18 -0400")
>>>>> "James" == James Hanley <jhanley@dgtlrift.com> writes:
James> Right now, buildroot downloads sources from released tarball urls, it
James> would be great if they could also pull from source repositories (git,
James> svn, etc.) to get unreleased features. For example I ran into an issue
James> with uclibc which was fixed but not yet released. It may also assist
James> in weeding out integration issues before package release.
I see Thomas already answered you, but what problem was this exactly and
what uClibc git commit fixed it? Probably we can backport it to 0.9.32
and include it in buildroot.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-07-07 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 14:06 [Buildroot] Feature request - pull sources from repose James Hanley
2011-07-07 14:19 ` Thomas Petazzoni
2011-07-07 15:12 ` Thomas Petazzoni
2011-07-07 17:22 ` Peter Korsgaard [this message]
2011-07-08 16:36 ` James Hanley
2011-07-08 18:07 ` 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=87wrfuqa4e.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.