unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "J.P." <jp@neverwas.me>
Cc: Michael Albinus <michael.albinus@gmx.de>,
	emacs-erc@gnu.org, 54536@debbugs.gnu.org
Subject: bug#54536: 29.0.50; Improve ERC's handling of multiline prompt input
Date: Sat, 26 Mar 2022 17:44:37 +0100	[thread overview]
Message-ID: <87bkxsd5oq.fsf__3004.31212397001$1648313120$gmane$org@gnus.org> (raw)
In-Reply-To: <87ee2p3kgx.fsf@neverwas.me> (J. P.'s message of "Fri, 25 Mar 2022 12:23:10 -0700")

"J.P." <jp@neverwas.me> writes:

> BTW, I think these can go:
>
>   refs/heads/features/erc-message-tags
>   refs/heads/fix/bug-34657-erc-hooks
>
> Is it customary to contact the authors before deleting?

If the branches have been merged (or their contents have been applied to
the trunk otherwise), it's OK to delete them.  If not, it's better to
contact the authors first.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-03-26 16:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 13:26 29.0.50; Improve ERC's handling of multiline prompt input J.P.
2022-03-23 13:50 ` bug#54536: " Lars Ingebrigtsen
     [not found] ` <87czic93sa.fsf@gnus.org>
2022-03-24 19:50   ` J.P.
2022-03-24 20:16     ` Michael Albinus
     [not found]     ` <8735j7jecz.fsf@gmx.de>
2022-03-24 23:38       ` J.P.
     [not found]       ` <87tubm53ar.fsf@neverwas.me>
2022-03-25 15:29         ` Lars Ingebrigtsen
     [not found]         ` <874k3mf3th.fsf@gnus.org>
2022-03-25 19:23           ` J.P.
2022-03-26 16:44             ` Lars Ingebrigtsen [this message]
     [not found]   ` <87ee2rb04e.fsf@neverwas.me>
2022-03-25 15:31     ` Lars Ingebrigtsen
     [not found]     ` <87zgledp6a.fsf@gnus.org>
2022-03-25 19:20       ` J.P.
2022-04-23  3:17 ` J.P.
2022-04-29 13:05 ` J.P.
2022-05-17 13:10 ` J.P.
     [not found] ` <874k1os3te.fsf@neverwas.me>
2022-05-17 22:48   ` Will Mengarini via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <YoQmVCugPRXY58eO@eskimo.com>
2022-05-18  1:34     ` J.P.
     [not found] <ADC23CE3-E6A4-4FF8-B033-174F60B2D59E@getmailspring.com>
2022-04-03 19:44 ` J.P.
     [not found] <87y20m7xzs.fsf@neverwas.me>
2022-04-03 20:15 ` Matheus Fillipe

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='87bkxsd5oq.fsf__3004.31212397001$1648313120$gmane$org@gnus.org' \
    --to=larsi@gnus.org \
    --cc=54536@debbugs.gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=jp@neverwas.me \
    --cc=michael.albinus@gmx.de \
    /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).