public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Mark Mitchell" <mark@codesourcery.com>
To: "Gabriel Dos Reis" <gdr@integrable-solutions.net>
Cc: "Andrew Haley" <aph@redhat.com>, <gcc@gcc.gnu.org>
Subject: Re: Converting to ISO C89
Date: Mon, 14 Apr 2003 11:21:00 -0000	[thread overview]
Message-ID: <003101c3022d$41bc4ff0$6900a8c0@minax> (raw)
In-Reply-To: <m3brzbvpfn.fsf@uniton.integrable-solutions.net>

Good point.

Given that, I'd prefer not to see ISO C89 patches making their way into the
3.3 branch.  That seems like more disruption than we need at this point.

Thanks,

-- Mark

----- Original Message -----
From: "Gabriel Dos Reis" <gdr@integrable-solutions.net>
To: "Mark Mitchell" <mark@codesourcery.com>
Cc: "Andrew Haley" <aph@redhat.com>; <gcc@gcc.gnu.org>
Sent: Saturday, April 12, 2003 6:02 AM
Subject: Re: Converting to ISO C89


> Mark Mitchell <mark@codesourcery.com> writes:
>
> | On Thu, 2003-04-10 at 07:25, Andrew Haley wrote:
> | > Mark Mitchell writes:
> | >  >
> | >  > The SC has finally finished voting on ISO C89 conversion.  (The
> | >  > mailing list for the SC experienced some problems, which caused
things
> | >  > to bog down a bit.)
> | >  >
> | >  > The verdict is in: it is OK to assume ISO C89 in all code in GCC
> | >  > proper.  (In other words, libiberty and/or other libraries are not
> | >  > affected.)
> | >  >
> | >  > So, patches to do ISO C conversions on the mainline are hereby
> | >  > pre-approved with one caveat: I would appreciate it if people would
> | >  > wait until GCC 3.3 is out the door.  The reason is that we're still
> | >  > applying a lot of patches to both branches, and that process is
tricky
> | >  > enough without creating a lot of spurious merge conflicts.
> | >
> | > I take it that new patches which are written in ISO C may be applied
> | > to the 3.3 branch.
> |
> | I can't see why not.
>
> That means that you would also have to OK the patch
>
>    http://gcc.gnu.org/ml/gcc/2003-03/msg01765.html
>
> for gcc-3_3-branch.
>
> -- Gaby
>

  reply	other threads:[~2003-04-14  2:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  7:12 Mark Mitchell
2003-03-25 12:12 ` Gabriel Dos Reis
2003-03-25 17:38   ` Mark Mitchell
2003-03-25 18:25     ` Kaveh R. Ghazi
2003-03-25 20:38       ` Raja R Harinath
2003-03-25 21:55         ` Zack Weinberg
2003-03-25 22:02           ` Falk Hueffner
2003-03-25 22:17             ` Zack Weinberg
2003-03-25 22:25               ` Falk Hueffner
2003-03-26  9:19                 ` Gabriel Dos Reis
2003-03-26  0:05               ` Joe Buck
2003-03-26  6:56                 ` Zack Weinberg
2003-03-25 22:13           ` Raja R Harinath
2003-03-25 22:23             ` tm_gccmail
2003-03-25 22:26               ` Joe Buck
2003-03-25 22:40               ` Raja R Harinath
2003-03-26  8:49           ` Gabriel Dos Reis
2003-03-26  9:55             ` Zack Weinberg
2003-04-06  2:11       ` Alexandre Oliva
2003-04-06  2:46         ` Zack Weinberg
2003-04-06  2:47           ` Alexandre Oliva
2003-04-06  3:15             ` Kaveh R. Ghazi
2003-04-06  4:40               ` Geoff Keating
2003-04-06 16:23                 ` Kaveh R. Ghazi
2003-03-30 12:45 ` Gabriel Dos Reis
2003-03-31  5:17   ` Mark Mitchell
2003-04-03  1:06     ` Zack Weinberg
2003-04-12 17:59       ` Gabriel Dos Reis
2003-04-12 18:06         ` Kaveh R. Ghazi
2003-04-10 15:31 ` Andrew Haley
2003-04-10 16:42   ` Mark Mitchell
2003-04-12 19:32     ` Gabriel Dos Reis
2003-04-14 11:21       ` Mark Mitchell [this message]
2003-04-14 12:57         ` Andrew Haley
2003-04-16 10:42           ` Andrew Haley
2003-04-16 17:25             ` Kaveh R. Ghazi

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='003101c3022d$41bc4ff0$6900a8c0@minax' \
    --to=mark@codesourcery.com \
    --cc=aph@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).