From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: custom-manual typos
Date: Fri, 27 Feb 2004 09:31:05 +0900 [thread overview]
Message-ID: <b9yhdxd5po6.fsf@jpl.org> (raw)
In-Reply-To: <871xohmmd0.fsf@zip.com.au>
>>>>> In <871xohmmd0.fsf@zip.com.au>
>>>>> Kevin Ryde <user42@zip.com.au> wrote:
> A few customize manual links that seem to have bit rotted,
> * gnus.el (gnus-group, gnus-summary, gnus-summary-sort): Corrections
> to custom-manual links.
> * gnus-art.el (gnus-article): Ditto.
> * mm-decode.el (mime-display, mime-security): Ditto.
I've commited it. Thanks.
--
Katsumi Yamaoka <yamaoka@jpl.org>
prev parent reply other threads:[~2004-02-27 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 23:50 Kevin Ryde
2004-02-27 0:31 ` Katsumi Yamaoka [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=b9yhdxd5po6.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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 NNTP newsgroup(s).