From: Lars Ingebrigtsen <larsi@gnus.org>
To: "João Pedro" <jpedrodeamorim@gmail.com>
Cc: 55754@debbugs.gnu.org
Subject: bug#55754: 28.1; rcirc-define-command interactive spec doesn't work
Date: Fri, 03 Jun 2022 05:24:50 +0200 [thread overview]
Message-ID: <87pmjqbf99.fsf@gnus.org> (raw)
In-Reply-To: <87wndyim7v.fsf@gmail.com> ("João Pedro"'s message of "Thu, 02 Jun 2022 22:12:36 -0300")
João Pedro <jpedrodeamorim@gmail.com> writes:
> Oh, thank you for the quick response and sorry for reporting a duplicate
> bug (I presume).
No problem -- I don't think that fix was due to a bug report, so it's no
duplication. :-)
> I'll take the opportunity to ask: where can I look for before filing a
> bug, in order to avoid creating duplicate reports or reports for stuff
> that was already fixed, even if not reported through debbugs? Just look
> for the patches on the dev mailing list or skim over the commits?
Yes, skimming commits is probably the only way. Some things are fixed
due to bug reports, but a lot of stuff gets fixed without one (when a
developer discovers the problem themselves).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-06-03 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 16:10 bug#55754: 28.1; rcirc-define-command interactive spec doesn't work João Pedro
2022-06-02 9:33 ` Lars Ingebrigtsen
2022-06-03 1:12 ` João Pedro
2022-06-03 3:24 ` Lars Ingebrigtsen [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
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=87pmjqbf99.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55754@debbugs.gnu.org \
--cc=jpedrodeamorim@gmail.com \
/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).