From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Cleaning up rcirc
Date: Mon, 13 Sep 2021 10:50:49 +0200 [thread overview]
Message-ID: <87sfy8g8pi.fsf@gnus.org> (raw)
In-Reply-To: <875yv7dqw7.fsf@posteo.net> (Philip Kaludercic's message of "Sat, 11 Sep 2021 16:21:44 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> Unless there are any objections, I would like to suggest merging the
> branch into master, as from what I gather the master branch will be cut
> off soon.
Sure go ahead and merge.
> Finally, because of my work on rcirc, it might make sense to add me as a
> maintainer in the header, so that anyone submitting a bug might Cc me in
> the report. Would that be ok, or is there some procedure for these kinds
> of things?
Yes, adding yourself as the maintainer here is the right thing to do.
> Oh, and another thing I was thinking about. Currently the default value
> for rcirc-server-alist connects the user to irc.libera.chat and lets
> them join #rcirc. I was wondering if it would be ok to add #emacs to
> this list too, seeing as rcirc is implied to be the default IRC client
> for Emacs (by "M-x irc"). I can imagine that since the channel is not
> directly affiliated to the GNU project, that there might be objections?
Adding #emacs is fine, I think.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-13 8:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 16:21 Cleaning up rcirc Philip Kaludercic
2021-09-11 16:49 ` Tassilo Horn
2021-09-11 17:49 ` Philip Kaludercic
2021-09-11 18:32 ` Tassilo Horn
2021-09-11 20:13 ` Philip Kaludercic
2021-09-11 21:01 ` Tassilo Horn
2021-09-13 22:59 ` chad
2021-09-21 18:52 ` Tassilo Horn
2021-09-21 19:18 ` Philip Kaludercic
2021-09-21 19:47 ` Tassilo Horn
2021-09-25 16:34 ` Philip Kaludercic
2021-09-26 8:20 ` Tassilo Horn
2021-09-11 17:56 ` Stefan Monnier
2021-09-11 20:16 ` Philip Kaludercic
2021-09-13 8:50 ` Lars Ingebrigtsen [this message]
2021-09-13 9:53 ` Stefan Kangas
2021-09-13 10:20 ` Tassilo Horn
2021-09-13 15:00 ` Amin Bandali
-- strict thread matches above, loose matches on Subject: below --
2021-06-04 15:16 Philip Kaludercic
2021-06-04 16:55 ` Andreas Schwab
2021-06-04 18:09 ` Philip Kaludercic
2021-06-06 18:41 ` Tassilo Horn
2021-06-06 21:09 ` Philip Kaludercic
2021-06-10 15:50 ` Philip Kaludercic
2021-06-10 19:13 ` Tassilo Horn
2021-06-10 21:54 ` Philip Kaludercic
2021-06-11 5:02 ` Tassilo Horn
2021-06-11 6:35 ` Tassilo Horn
2021-06-11 9:08 ` Philip Kaludercic
2021-06-11 9:27 ` Tassilo Horn
2021-06-11 9:44 ` Philip Kaludercic
2021-06-11 11:10 ` Tassilo Horn
2021-06-11 14:51 ` Philip Kaludercic
2021-06-11 8:09 ` Philip Kaludercic
2021-06-07 9:55 ` Lars Ingebrigtsen
2021-07-22 22:14 ` Philip Kaludercic
2021-07-22 22:18 ` Lars Ingebrigtsen
2021-06-06 17:53 ` Bone Baboon
2021-06-07 13:08 ` Zhiwei Chen
2021-06-07 13:20 ` Philip Kaludercic
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=87sfy8g8pi.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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).