From: Eli Zaretskii <eliz@gnu.org>
To: Michael Olson <mwolson@gnu.org>
Cc: emacs-erc@gnu.org, bandali@gnu.org, jp@neverwas.me,
53617@debbugs.gnu.org, strings.stringsandstrings@gmail.com,
larsi@gnus.org
Subject: bug#53617: 28.0.90; duplicate checks in erc--switch-to-buffer
Date: Mon, 31 Jan 2022 14:31:06 +0200 [thread overview]
Message-ID: <83wnig84tx.fsf__19818.4602939122$1643639274$gmane$org@gnu.org> (raw)
In-Reply-To: <CAN4ruPiVd5Zp3H=vbX0XqR1-k=YWsuTOb5_rPBUtW-4UH+ma9A@mail.gmail.com> (message from Michael Olson on Sun, 30 Jan 2022 22:22:05 -0500)
> From: Michael Olson <mwolson@gnu.org>
> Date: Sun, 30 Jan 2022 22:22:05 -0500
> Cc: "J.P." <jp@neverwas.me>, strings.stringsandstrings@gmail.com,
> Eli Zaretskii <eliz@gnu.org>, emacs-erc@gnu.org, bandali@gnu.org, 53617@debbugs.gnu.org
>
> What I'd sometimes do 10+ years ago is keep an AUTHORS file with a list of who contributed, which files,
> and (in the case of unassigned contributors) how many lines so I knew if they were getting close to the limit.
> I'm not sure if that would map well to the Emacs repo, maybe a side file like ERC-AUTHORS, or just kept
> outside of the repo.
This is very tedious, and moreover, ephemeral: the threshold of a
dozen or so non-trivial lines is crossed only once and usually very
quickly; once it is crossed, it can never be crossed back (well,
except in the rare case that a person changes employers and is again
without an assignment). So this kind of bookkeeping requires a lot of
clerical work for little or no gain.
next prev parent reply other threads:[~2022-01-31 12:31 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
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 [this message]
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='83wnig84tx.fsf__19818.4602939122$1643639274$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=53617@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
--cc=larsi@gnus.org \
--cc=mwolson@gnu.org \
--cc=strings.stringsandstrings@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).