From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "stefan@marxist.se" <stefan@marxist.se>,
"17567@debbugs.gnu.org" <17567@debbugs.gnu.org>
Subject: bug#17567: [External] : Re: bug#17567: 24.4.50; doc string of `define-derived-mode'
Date: Sat, 25 Sep 2021 18:59:13 +0000 [thread overview]
Message-ID: <SJ0PR10MB54889FB1D752945013FC7FDAF3A59@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83lf3kpkdt.fsf@gnu.org>
> > No, I won't try to verify your fix by downloading the
> > updated files from master etc. If you'd posted the
> > new doc string in the bug thread I could easily have,
> > and would have, gladly checked it.
>
> There's no need to download anything, the up-to-date sources can be
> browsed on the Savannah's Emacs project page using your Web browser.
As I said, if the updated doc string is posted
in the bug-report thread then I'll be glad to
check it (whether with a web browser or a mail
client).
But no, I'm not going to go to Savannah, find
the Emacs project page, and dig out the source
code. Not for a doc string correction. Far
easier, and clearer for everyone, to post the
doc string in the bug thread, where it will
remain forever as part of that thread.
next prev parent reply other threads:[~2021-09-25 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 19:15 bug#17567: 24.4.50; doc string of `define-derived-mode' Drew Adams
2014-05-23 19:35 ` Drew Adams
2021-09-25 17:15 ` Stefan Kangas
2021-09-25 17:30 ` Eli Zaretskii
2021-09-25 18:01 ` Stefan Kangas
2021-09-25 18:46 ` Eli Zaretskii
2021-09-25 19:07 ` Stefan Kangas
2021-09-25 19:11 ` Eli Zaretskii
2021-09-25 19:38 ` Stefan Kangas
2021-09-25 17:36 ` bug#17567: [External] : " Drew Adams
2021-09-25 18:42 ` Eli Zaretskii
2021-09-25 18:59 ` Drew Adams [this message]
2021-09-25 19:05 ` Eli Zaretskii
2021-09-25 19:44 ` Drew Adams
2021-09-25 19:53 ` Eli Zaretskii
2021-09-25 21:08 ` Drew Adams
2021-09-27 22:36 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB54889FB1D752945013FC7FDAF3A59@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=17567@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).