public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@hack.frob.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>,    <libc-ports@sourceware.org>
Subject: Re: Ports-related README updates
Date: Wed, 05 Dec 2012 22:13:00 -0000	[thread overview]
Message-ID: <20121205221330.558642C0C3@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of  Wednesday, 5 December 2012 22:07:57 +0000 <Pine.LNX.4.64.1212052205010.13635@digraph.polyomino.org.uk>

Looks fine to me.

> +git.  To report a bug in code housed in the ports add-on, please go to
> +http://sources.redhat.com/bugzilla/ and file a bug report under the
> +glibc "ports" component.

This is unrelated to your change and I just noticed it because you refilled
the paragraph, but all URLs should use sourceware.org nowadays rather than
sources.redhat.com.

      reply	other threads:[~2012-12-05 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 22:08 Joseph S. Myers
2012-12-05 22:13 ` Roland McGrath [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=20121205221330.558642C0C3@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    /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).