From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix PRs glibc/{93,94,98,107}
Date: Wed, 21 Apr 2004 19:02:00 -0000 [thread overview]
Message-ID: <200404211902.i3LJ2iao005165@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Wednesday, 21 April 2004 12:24:09 +0200 <20040421102409.GE5191@sunsite.ms.mff.cuni.cz>
> Selected obvious fixes from glibc bugzilla.
I think we should start a convention for mentioning bug #s in log entries.
Some rigid format that regexps can match easily. I think we can then set
something up so the commits with matching entries automagically add
comments to bugzilla.
> 2004-04-21 Jakub Jelinek <jakub@redhat.com>
>
> * posix/tst-chmod.c (do_test): Fix a typo.
> * elf/lateglobal.c (main): Fix error checks.
> Patch by Stephen Clarke <stephen.clarke@st.com>.
These are separate, a blank line should be between them.
> * manual/ctype.texi (isblank, iswblank): Mark as ISO functions,
> mention they have been added in ISO C99.
I've changed these to say that these were originally GNU extensions.
> * manual/summary.texi: Rebuilt.
> Reported by Ben Pfaff <blp@cs.stanford.edu>.
This generated file is not in CVS at all.
> 2004-03-31 H.J. Lu <hongjiu.lu@intel.com>
>
> * sysdeps/ieee754/ldbl-128/bits/huge_vall.h: Fix typo.
I've put all these in with the changes mentioned.
next prev parent reply other threads:[~2004-04-21 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 12:35 Jakub Jelinek
2004-04-21 18:58 ` Ulrich Drepper
2004-04-21 19:02 ` Roland McGrath [this message]
2004-04-21 22:39 ` Petter Reinholdtsen
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=200404211902.i3LJ2iao005165@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--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).