unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manphiz <manphiz@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 65882-done@debbugs.gnu.org,
	Philip Kaludercic <philipk@posteo.net>,
	Ryan Yeske <rcyeske@gmail.com>, Leo Liu <sdl.web@gmail.com>
Subject: bug#65882: 29.1; rcirc doesn't rejoin channels automatically on reconnecting
Date: Fri, 22 Sep 2023 14:37:13 -0700	[thread overview]
Message-ID: <87fs3528l2.fsf@debian-hx90.lan> (raw)
In-Reply-To: <CADwFkmm-N7n_etuYz1N=jSBvNE22jQ2a+0bM_vjAD90ay7UTRQ@mail.gmail.com> (Stefan Kangas's message of "Fri, 22 Sep 2023 01:46:14 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>>> Additionally, is it OK to backport this to 29 branch or even 28 branch?
>>
>> I don't know if bugs are backported onto emacs-28, the branch seems to
>> be stale.
>
> We don't plan to make any more releases of Emacs 28, so we don't bother
> with backporting fixes there.
>
>> The emacs-29 branch might be viable, but I don't want to decide that
>> myself.  If Stefan is fine with that, I can take care of it.
>
> I don't necessarily object, but is it a regression?

The reconnecting and rejoining channels feature is broken in certain
situation, and this patch fixes that.  Some other users claimed this
works for them, so I would say this may be considered a regression.

> Is the change safe?

According to the logic of the code, this patch enables doing work that
(I believe) should have been done and not changing anything else, so I
would say it is safe.

> If the answer to either of those questions is "no", I think master is
> the safer choice.
>

I would say the answers are both yes, but of course that's just my
opinion and the decision is up to you :)

>>> Or is there any automatic backport process for release branches?
>>
>> Not that I know of.
>
> The process is indeed manual.

-- 
Manphiz





  reply	other threads:[~2023-09-22 21:37 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
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 [this message]
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=87fs3528l2.fsf@debian-hx90.lan \
    --to=manphiz@gmail.com \
    --cc=65882-done@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).