From: Peter Korsgaard <peter.korsgaard@barco.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH][RESEND] libgcc_s still missing
Date: Thu, 16 Nov 2006 10:59:45 +0100 [thread overview]
Message-ID: <87zmarogoe.fsf@sleipner.barco.com> (raw)
In-Reply-To: <20061115200659.GA24410@tuxedo.home.lan> (Lars Munch's message of "Wed, 15 Nov 2006 21:07:00 +0100")
>>>>> "LM" == Lars Munch <lars@segv.dk> writes:
Hi Lars,
LM> This patch got ignored the first time, so here it is again:
Huh, I thought I already comitted it, but apparently not.
Sorry about that - it's now checked in as r16536.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2006-11-16 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 20:07 [Buildroot] [PATCH][RESEND] libgcc_s still missing Lars Munch
2006-11-16 9:59 ` 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=87zmarogoe.fsf@sleipner.barco.com \
--to=peter.korsgaard@barco.com \
--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