From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19070@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org
Subject: bug#19070: 25.0.50; Provide a user option that filters the buffer list for `switch-to-next-buffer'
Date: Thu, 12 May 2022 23:57:01 +0200 [thread overview]
Message-ID: <87v8uaifde.fsf@gmail.com> (raw)
In-Reply-To: <83lev6obye.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 May 2022 21:14:17 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Put a direct link to the result (code or doc) in the
>> close message.
>
> It's a burden. Once again, here's the URL for the Git Web access:
>
> https://git.savannah.gnu.org/cgit/emacs.git
Note that this page provides a search engine to scan commit messages, so
looking for a change related to a bug number or a symbol is
straightforward (since ChangeLog entries tend to include this
information):
https://git.savannah.gnu.org/cgit/emacs.git/log/?qt=grep&q=bug.19070
https://git.savannah.gnu.org/cgit/emacs.git/log/?qt=grep&q=switch-to-prev-buffer-skip-regexp
Your browser might have a feature to "add a keyword for this search" if
you right-click the input field (Firefox has that, at any rate), so
finding the answer to the question "how was bug#19070 fixed" can be as
simple as typing…
> emacs.git bug#19070
… in your URL bar.
Hope that helps.
next prev parent reply other threads:[~2022-05-12 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 16:38 bug#19070: 25.0.50; Provide a user option that filters the buffer list for `switch-to-next-buffer' Drew Adams
2022-05-12 1:35 ` Lars Ingebrigtsen
2022-05-12 16:02 ` Drew Adams
2022-05-12 16:47 ` Eli Zaretskii
2022-05-12 16:53 ` Drew Adams
2022-05-12 17:06 ` Eli Zaretskii
2022-05-12 17:25 ` Drew Adams
2022-05-12 17:37 ` Eli Zaretskii
2022-05-12 17:50 ` Drew Adams
2022-05-12 18:14 ` Eli Zaretskii
2022-05-12 21:57 ` Kévin Le Gouguec [this message]
2022-05-13 8:14 ` Robert Pluim
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=87v8uaifde.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=19070@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=larsi@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.
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).