From: Stefan Kangas <stefankangas@gmail.com>
To: Nicholas Savage <nick@nicksavage.ca>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39912@debbugs.gnu.org
Subject: bug#39912: "Probably introduced at or before Emacs version ..." link should open NEWS read-only
Date: Tue, 8 Sep 2020 13:54:36 +0000 [thread overview]
Message-ID: <CADwFkm=_CC0o_rL1zPo74wrE1wC4adFQz8XTFt=Y1RtOOxJtcQ@mail.gmail.com> (raw)
In-Reply-To: <7843e1b5-d84e-4955-a671-90d32121ac81@www.fastmail.com>
"Nicholas Savage" <nick@nicksavage.ca> writes:
> I'm going to attempt a fix for this, it seems like a simple enough fix
> for me to tackle for my first patch here.
Thanks; this does look like an excellent choice for a first patch.
You can find some pointers on best practices for how to format your
patch, etc. in the CONTRIBUTE file. Let us know if you have any
questions.
next prev parent reply other threads:[~2020-09-08 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 18:22 bug#39912: 27.0.90; Probably introduced at or before Emacs version Felician Nemeth
2020-09-07 19:54 ` bug#39912: "Probably introduced at or before Emacs version ..." link should open NEWS read-only Nicholas Savage
2020-09-07 21:00 ` Lars Ingebrigtsen
2020-09-08 6:59 ` Andreas Schwab
2020-09-08 7:25 ` Stefan Kangas
2020-09-08 7:26 ` Andreas Schwab
2020-09-08 10:26 ` Lars Ingebrigtsen
[not found] ` <871rjdi0wb.fsf@nicksavage.ca>
[not found] ` <87v9go4kzq.fsf@gnus.org>
2020-09-08 11:26 ` Nicholas Savage
2020-09-08 13:54 ` Stefan Kangas [this message]
2020-09-08 20:27 ` bug#39912: [PATCH] Open describe-function links in view-mode (Bug#39912) Nicholas Savage
2020-09-08 21:01 ` Stefan Kangas
2020-09-08 21:04 ` Lars Ingebrigtsen
2020-09-09 0:14 ` Nicholas Savage
2020-09-09 9:39 ` Lars Ingebrigtsen
2020-09-10 0:43 ` Nicholas Savage
2020-09-10 13:19 ` Lars Ingebrigtsen
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='CADwFkm=_CC0o_rL1zPo74wrE1wC4adFQz8XTFt=Y1RtOOxJtcQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=39912@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=nick@nicksavage.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.