Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix compilation on the recent glibc CVS snapshot
Date: Wed, 08 Aug 2007 22:15:00 -0000	[thread overview]
Message-ID: <20070808221443.GA11800@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3ps1xu1hz.fsf@codesourcery.com>

On Thu, 09 Aug 2007 00:04:24 +0200, Jim Blandy wrote:
> Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> > 2007-08-08  Jan Kratochvil  <jan.kratochvil@redhat.com>
> >
> > 	* serial.c (serial_open): Fix OPEN parameter macro expansion.
> 
> POSIX System Interfaces section 2.1 says, "Any function declared in a
> header may also be implemented as a macro defined in the header."  I
> gather this means that GLIBC is within its rights to make that change
> to 'open'.  I've learned something new today.

Thanks, me too.


> So, this change is approved.

Committed.


Regards,
Jan


      reply	other threads:[~2007-08-08 22:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 20:55 Jan Kratochvil
2007-08-08 22:04 ` Jim Blandy
2007-08-08 22:15   ` Jan Kratochvil [this message]

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=20070808221443.GA11800@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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