From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb
Date: Tue, 01 Jun 2010 12:56:57 +0200 [thread overview]
Message-ID: <8739x7rpfq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1275387811.1624.6.camel@ubuntu> (Microbit Ubuntu's message of "Tue, 01 Jun 2010 20:23:31 +1000")
>>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:
Hi,
>> Both issues should be fixed in git now.
>>
Microbit> Thanks for reviewing.
Microbit> Does this mean the fix is also in final 2010.05 tarball ?
Microbit> (I'm not used to git, I probably should learn, have been thinking about
Microbit> using it for my CVS)
Yes.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-06-01 10:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 12:43 [Buildroot] Buildroot 2010.05-rc3 released Peter Korsgaard
2010-05-27 18:58 ` Microbit_Ubuntu
2010-05-27 21:15 ` Yann E. MORIN
2010-05-27 21:51 ` Microbit_Ubuntu
2010-05-27 21:55 ` Microbit_Ubuntu
2010-05-28 20:20 ` Yann E. MORIN
2010-06-01 10:21 ` Microbit_Ubuntu
2010-06-01 10:57 ` Peter Korsgaard
2010-06-01 18:25 ` Microbit_Ubuntu
2010-06-01 20:21 ` Microbit_Ubuntu
2010-06-01 20:27 ` Yann E. MORIN
2010-05-28 0:49 ` Microbit_Ubuntu
2010-05-27 21:11 ` [Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ? Microbit_Ubuntu
2010-05-27 21:19 ` Yann E. MORIN
2010-05-27 21:32 ` Microbit_Ubuntu
2010-05-28 12:44 ` Peter Korsgaard
2010-06-01 10:38 ` Microbit_Ubuntu
2010-06-01 11:00 ` Peter Korsgaard
2010-05-28 0:37 ` [Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb Microbit_Ubuntu
2010-05-30 7:35 ` Peter Korsgaard
2010-06-01 10:23 ` Microbit_Ubuntu
2010-06-01 10:56 ` Peter Korsgaard [this message]
2010-06-01 18:30 ` Microbit_Ubuntu
2010-06-15 7:10 ` Thomas Petazzoni
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=8739x7rpfq.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.