From: Richard Strand <richard.strand@icomera.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: [PATCH 0 of 1] Remove documentation references to the seemingly native toolchain issue
Date: Fri, 08 Jan 2010 18:57:00 -0000 [thread overview]
Message-ID: <patchbomb.1262976984@richard-laptop> (raw)
Hi Yann,
I've created a patch which removes the references in the documentation to the
seeming native toolchain issue. This is because the issue seems to be fixed
now that glic and eglibc are hard-coded to compile with -O2.
I know this is a fairly trivial patch and I mainly created it to test
mercurial, but it doesn't make sense to list this as an issue if it isn't.
Regards,
Richard Strand
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2010-01-08 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 18:57 Richard Strand [this message]
2010-01-08 18:57 ` [PATCH 1 of 1] documentation: Remove refs to seemingly native toolchains issue Richard Strand
2010-01-09 18:23 ` [PATCH 0 of 1] Remove documentation references to the seemingly native toolchain issue Yann E. MORIN
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=patchbomb.1262976984@richard-laptop \
--to=richard.strand@icomera.com \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).