public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug manual/5805] patch improving details in texinfo manual
Date: Fri, 17 Feb 2012 17:47:00 -0000 [thread overview]
Message-ID: <bug-5805-131-aq2qJaPrQD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-5805-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=5805
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-17 17:46:58 UTC ---
The problems with lines that were wrongly split had already been fixed; I've
applied the rest of the patch (minus the bits that just added or removed blank
lines), thanks. As the changes here were just some mechanical fixes applied
everywhere it could go in without needing a copyright assignment, but if you
make less mechanical changes to glibc in future then the paperwork will be
needed.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next parent reply other threads:[~2012-02-17 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-5805-131@http.sourceware.org/bugzilla/>
2012-02-17 17:47 ` jsm28 at gcc dot gnu.org [this message]
2014-07-02 7:01 ` fweimer at redhat dot com
2008-02-28 23:33 [Bug manual/5805] New: " nicolas dot boulenguez at free dot fr
2008-02-28 23:35 ` [Bug manual/5805] " nicolas dot boulenguez at free dot fr
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=bug-5805-131-aq2qJaPrQD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).