From: Manphiz <manphiz@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 65882@debbugs.gnu.org, Ryan Yeske <rcyeske@gmail.com>,
Stefan Kangas <stefankangas@gmail.com>,
Leo Liu <sdl.web@gmail.com>
Subject: bug#65882: 29.1; rcirc doesn't rejoin channels automatically on reconnecting
Date: Thu, 21 Sep 2023 08:00:55 -0700 [thread overview]
Message-ID: <87a5tf3714.fsf@debian-hx90.lan> (raw)
In-Reply-To: <878r97ooxs.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 15 Sep 2023 07:50:23 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> The change makes sense, but I'll want to try it out to make sure we are
> doing the right thing. Unless I write something here, ping me in a few
> days. These kinds of auto-reconnect bugs can be annoying to debug in
> real-life situations.
>
Friendly ping.
> Manphiz <manphiz@gmail.com> writes:
>
>> Stefan Kangas <stefankangas@gmail.com> writes:
>>
>>> severity 65882 + minor
>>> thanks
>>>
>>> Manphiz <manphiz@gmail.com> writes:
>>>
>>>> I noticed that you lowered the severity of this bug from "normal" to
>>>> "wishlist". AIUI rcirc provides a way to automatically join channels
>>>> upon connecting to a server and currently this is not working as
>>>> intended, so IMHO it should be considered a bug instead of a feature
>>>> request (a wishlist).
>>>
>>> Thanks, so I bumped it to minor. I hope that makes more sense.
>>>
>>
>> Thanks!
>>
>>>> (If you are using severity as a means to manage bug triage priority
>>>> I'm OK with that.)
>>>
>>> My impression is that almost no one pays attention to bug severities, so
>>> I wouldn't make too much of it. Bug reports that come with a patch,
>>> like yours did, tend to get more visibility though.
>>>
>>
>> Ah got it. It's my first time filing bug here so not very familiar with
>> the convention. Looks like tagging patch was a good move :)
>
> So this patch would be applied without a copyright assignment, right?
>
>>>> Personally, as the patch is sufficiently trivial, I would hope it won't
>>>> take too much work for a review. But I would understand if dealing with
>>>> rcirc-user-authenticated is more involved than it looks like and should
>>>> be handled with care.
>>>
>>> I've copied in the rcirc maintainers. Let's see if they have any
>>> comments first.
>>
>> Great! Thanks again!
--
Manphiz
next prev parent reply other threads:[~2023-09-21 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 0:58 bug#65882: 29.1; rcirc doesn't rejoin channels automatically on reconnecting Manphiz
2023-09-14 22:57 ` Manphiz
2023-09-15 2:27 ` Stefan Kangas
2023-09-15 5:30 ` Manphiz
2023-09-15 7:50 ` Philip Kaludercic
2023-09-15 8:15 ` Manphiz
2023-09-21 15:00 ` Manphiz [this message]
2023-09-21 16:27 ` Philip Kaludercic
2023-09-21 16:57 ` Manphiz
2023-09-22 8:23 ` Philip Kaludercic
2023-09-22 8:46 ` Stefan Kangas
2023-09-22 21:37 ` Manphiz
2023-09-23 11:41 ` Stefan Kangas
2023-09-23 12:43 ` Philip Kaludercic
2023-09-23 22:34 ` Manphiz
2023-09-14 22:57 ` Manphiz
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=87a5tf3714.fsf@debian-hx90.lan \
--to=manphiz@gmail.com \
--cc=65882@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=rcyeske@gmail.com \
--cc=sdl.web@gmail.com \
--cc=stefankangas@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).