GNU bug report logs - #55754
28.1; rcirc-define-command interactive spec doesn't work

Previous Next

Full log

Message #16 received at 55754 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: João Pedro <jpedrodeamorim <at> gmail.com>
Cc: 55754 <at> debbugs.gnu.org
Subject: Re: bug#55754: 28.1; rcirc-define-command interactive spec doesn't
 work
Date: Fri, 03 Jun 2022 05:24:50 +0200

João Pedro <jpedrodeamorim <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.