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 19:44:50 +0000 [thread overview]
Message-ID: <SJ0PR10MB54882D251C0AB173228FA555F3A59@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83ee9cpjao.fsf@gnu.org>
> > 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).
>
> That's not how Emacs development works. People who want to track the
> development or participate in it are expected to access the Git
> repository.
If you'd like me to check the fix (Stefan's request)
then please consider putting the new text in the bug
thread. Otherwise, you'll just have to do without
my review and feedback, I guess. Not a biggee (the
bug was anyway closed, without such a review).
_I didn't request_ to review the fix ("participate"
in tracking the development). I was invited to do
so. I replied that if the text to review is in the
bug thread then I'll be glad to review it.
> > 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.
>
> ... If you refuse to do that, you are not helping
> the project as much as you could have.
If you refuse to put the updated doc string in a bug
thread that asks only for a doc-string fix, then
you're not helping users, or the project, as much as
you could. Copy...paste...send. Simple.
(I'd even consider that common courtesy, but you're
by no means obliged to see courtesy the same way,
of course.)
___
And if that review-request text is boilerplate (I
wonder now, as I see that it mentions using "Reply
to all" etc.) then you might consider adding a link
to it, to the fix (manually, if not automatically).
Please verify that this fix works for you, but for
now I'm closing this bug report. If you see
anything that is wrong, please reply to this email
(use "Reply to all" in your email client) and we
can reopen the bug report. You could also just
report a new bug.
Thanks again for the bug report!
next prev parent reply other threads:[~2021-09-25 19:44 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
2021-09-25 19:05 ` Eli Zaretskii
2021-09-25 19:44 ` Drew Adams [this message]
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=SJ0PR10MB54882D251C0AB173228FA555F3A59@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).