public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: Fix a number of warnings
Date: Sun, 03 Mar 2002 10:32:00 -0000	[thread overview]
Message-ID: <1015180329.23800.33.camel@myware.mynet> (raw)
In-Reply-To: <u8wuwtso32.fsf@gromit.moeb>

[-- Attachment #1: Type: text/plain, Size: 457 bytes --]

On Sun, 2002-03-03 at 06:49, Andreas Jaeger wrote:

> Ok to commit?

Yes.  But...

> 	* linuxthreads_db/thread_dbP.h: Include <unistd.h> for prototypes
> 	of __libc_write.

linuxthread_db also has its own ChangeLog file.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-03-03 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-03  7:14 Andreas Jaeger
2002-03-03 10:32 ` Ulrich Drepper [this message]
2002-03-03 11:37   ` Andreas Jaeger

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=1015180329.23800.33.camel@myware.mynet \
    --to=drepper@redhat.com \
    --cc=aj@suse.de \
    --cc=libc-hacker@sources.redhat.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).