public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, JonY <10walls@gmail.com>,
	NightStrike <nightstrike@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] gcc-8/porting_to.html
Date: Thu, 09 Mar 2017 11:22:00 -0000	[thread overview]
Message-ID: <b49480df-443e-95d1-881d-395be6ab874b@foss.arm.com> (raw)
In-Reply-To: <20170309105854.GG22703@tucnak>

Hi Jakub,

I forgot to mention "ok for stage1?", my bad. JonY said he was queuing the 
corresponding changes in GCC for stage1 so I was just trying to have a complete 
story. I do not expect to commit this before the actual code change is committed.

Best regards,

Thomas

On 09/03/17 10:58, Jakub Jelinek wrote:
> On Thu, Mar 09, 2017 at 10:51:27AM +0000, Thomas Preudhomme wrote:
>> Thanks Gerald,
>>
>> JonY: what about the attached patch to document the change of behavior of
>> GCC on Windows depending on the configure option used?
>
> GCC 7 has not branched yet, so the change can't be committed anywhere.
> It seems documenting something before it is actually changed is just too
> weird.
>
> 	Jakub
>

  reply	other threads:[~2017-03-09 11:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  9:49 [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows Thomas Preudhomme
2017-01-19  2:05 ` JonY
2017-01-20  9:06   ` Thomas Preudhomme
2017-01-26 13:19   ` Thomas Preudhomme
2017-02-07  8:48     ` JonY
2017-02-14  9:46       ` Thomas Preudhomme
2017-02-14 10:58         ` JonY
2017-02-17 11:01           ` JonY
2017-02-17 11:51             ` Thomas Preudhomme
2017-02-17 23:05               ` JonY
2017-02-22 16:07                 ` Thomas Preudhomme
     [not found]                   ` <CAF1jjLtsw10najrRwzJ7MJSSKxqmX0Wy4gKyf=dhmcAebS+JOA@mail.gmail.com>
2017-03-02 16:58                     ` Thomas Preudhomme
2017-03-04 14:25                       ` [wwwdocs] gcc-8/porting_to.html (was: [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows) Gerald Pfeifer
2017-03-09 10:51                         ` [wwwdocs] gcc-8/porting_to.html Thomas Preudhomme
2017-03-09 10:59                           ` Jakub Jelinek
2017-03-09 11:22                             ` Thomas Preudhomme [this message]
2017-03-09 13:16                               ` JonY
2017-03-12 14:08                           ` Gerald Pfeifer
2017-03-12 23:51                             ` JonY
2017-03-22 17:39                               ` Thomas Preudhomme
2017-03-22 22:51                                 ` JonY
2017-03-23  6:47                                 ` Gerald Pfeifer
2017-03-23 10:47                                   ` Thomas Preudhomme
2017-05-04 11:10                                     ` JonY
2017-05-04 14:37                                       ` Thomas Preudhomme
2017-05-04 14:43                                   ` Thomas Preudhomme
2017-05-04 15:17                 ` [arm-embedded] [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows Thomas Preudhomme

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=b49480df-443e-95d1-881d-395be6ab874b@foss.arm.com \
    --to=thomas.preudhomme@foss.arm.com \
    --cc=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=nightstrike@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).