From: Guy Gastineau <strings.stringsandstrings@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: larsi@gnus.org, emacs-erc@gnu.org, bandali@gnu.org,
53617@debbugs.gnu.org
Subject: bug#53617: 28.0.90; duplicate checks in erc--switch-to-buffer
Date: Sat, 29 Jan 2022 21:25:28 -0500 [thread overview]
Message-ID: <CAHgGP-LOmr2YpCYCGEHX9tUK6T4KfBZoeKW8JKK-42eKOQmqYg__43390.5302010075$1643509579$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <878ruyqf0b.fsf@neverwas.me>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Yeah, I should get my keys on some servers. I finally started signing all
my commits, so I just felt weird about not signing the patch. It was my
pleasure to contribute this miniscule addition to the wonderful emacs.
On Sat, Jan 29, 2022, 6:49 PM J.P. <jp@neverwas.me> wrote:
> Guy Gastineau <strings.stringsandstrings@gmail.com> writes:
>
> > Here it is. I don't think my pgp key is on any keyserver, but I signed
> > it anyway.
>
> I'm not sure if Emacs has a policy regarding the signing of everyday
> contributions, but if your key isn't signed by anyone and not propagated
> among the keyservers, then I'd guess you can probably just skip further
> signing in the near term.
>
> > Thank you for the encouragement.
>
> My pleasure. This looks ready for Emacs 29. Thanks.
>
> . . .
>
> I've added the customary tweaks to the log message if someone wants to
> glance at it (cc. bandali, Lars). Also, question: is there formal
> recordkeeping going on re exempt lines accumulated per individual? And
> if not, is the recommended way to get a tally just `git log --author=`?
>
>
[-- Attachment #2: Type: text/html, Size: 1579 bytes --]
next prev parent reply other threads:[~2022-01-30 2:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 0:10 bug#53617: 28.0.90; duplicate checks in erc--switch-to-buffer Guy Gastineau
2022-01-29 3:07 ` J.P.
2022-01-29 3:13 ` Guy Gastineau
2022-01-29 3:30 ` J.P.
2022-01-29 4:29 ` Guy Gastineau
2022-01-29 23:49 ` bug#53617: " J.P.
[not found] ` <878ruyqf0b.fsf@neverwas.me>
2022-01-30 2:25 ` Guy Gastineau [this message]
2022-01-30 6:34 ` Eli Zaretskii
[not found] ` <83a6fdbulb.fsf@gnu.org>
2022-01-30 15:43 ` J.P.
[not found] ` <878rux9ql2.fsf@neverwas.me>
2022-01-30 16:00 ` Lars Ingebrigtsen
[not found] ` <87bkztb4di.fsf@gnus.org>
2022-01-30 16:25 ` Guy Gastineau
2022-01-31 3:22 ` Michael Olson
2022-01-31 3:30 ` Emanuel Berg via General discussion about ERC
2022-01-31 3:38 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-31 5:35 ` J.P.
2022-01-31 12:31 ` Eli Zaretskii
2022-03-14 13:33 ` J.P.
2022-03-19 10:08 ` J.P.
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='CAHgGP-LOmr2YpCYCGEHX9tUK6T4KfBZoeKW8JKK-42eKOQmqYg__43390.5302010075$1643509579$gmane$org@mail.gmail.com' \
--to=strings.stringsandstrings@gmail.com \
--cc=53617@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
--cc=larsi@gnus.org \
/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).