From: nick clifton <nickc@redhat.com>
To: Diego Novillo <dnovillo@google.com>
Cc: bernds@codesourcery.com, jzhang918@gmail.com, gcc-patches@gcc.gnu.org
Subject: Re: Commit: BFIN: Fix use of VEC_last macro in bfin.c
Date: Fri, 17 Aug 2012 13:04:00 -0000 [thread overview]
Message-ID: <502E3FFE.5050707@redhat.com> (raw)
In-Reply-To: <502E3B19.8000201@google.com>
Hi Diego,
> Would it be too much imposition for you to put this on the wiki?
I would be happy to. Where do you think would be appropriate ? I would
guess that somewhere off the Getting Started page
(http://gcc.gnu.org/wiki/GettingStarted) would be best. Maybe a new
item in the Tutorials section, or an extra paragraph on the Testing_GCC
page ?
Cheers
Nick
next prev parent reply other threads:[~2012-08-17 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 9:55 Nick Clifton
2012-08-16 12:15 ` Diego Novillo
2012-08-17 7:17 ` nick clifton
2012-08-17 12:38 ` Diego Novillo
2012-08-17 13:04 ` nick clifton [this message]
2012-08-17 14:53 ` Joseph S. Myers
2012-08-17 15:01 ` Diego Novillo
2012-08-19 17:31 ` Gerald Pfeifer
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=502E3FFE.5050707@redhat.com \
--to=nickc@redhat.com \
--cc=bernds@codesourcery.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jzhang918@gmail.com \
/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).