From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Where do toolchain patches come from?
Date: Wed, 25 Oct 2006 20:34:51 +0200 [thread overview]
Message-ID: <20061025183451.GD5673@aon.at> (raw)
In-Reply-To: <E55CA8ECFBA85E4CB8E8173566B9EFEB287B55@rennsmail04.eu.thmulti.com>
On Wed, Oct 25, 2006 at 06:19:05PM +0200, Paugam Luc wrote:
>Hi All,
>
>Sorry to bother you, but I am wondering from where do toolchain patch
>files come from?
>
>E.g. toolchain/binutils/2.16.1/300-001_ld_makefile_patch.patch
Did you look at that particular patch?
next prev parent reply other threads:[~2006-10-25 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 16:19 [Buildroot] Where do toolchain patches come from? Paugam Luc
2006-10-25 18:34 ` Bernhard Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-26 8:29 Paugam Luc
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=20061025183451.GD5673@aon.at \
--to=rep.nop@aon.at \
--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.