From: Emanuel Berg via General discussion about ERC <emacs-erc@gnu.org>
To: emacs-erc@gnu.org
Cc: bug-gnu-emacs@gnu.org
Subject: Re: bug#53617: 28.0.90; duplicate checks in erc--switch-to-buffer
Date: Mon, 31 Jan 2022 04:30:30 +0100 [thread overview]
Message-ID: <87r18oa8fd.fsf@zoho.eu> (raw)
In-Reply-To: CAN4ruPiVd5Zp3H=vbX0XqR1-k=YWsuTOb5_rPBUtW-4UH+ma9A@mail.gmail.com
Michael Olson wrote:
>>> Apologies for the unintelligible mumblage.
>>> Somehow (believe it or not), I was trying to ask whether
>>> there's a system in place for keeping track of the number
>>> of non-trivial changes a non-paperwork holder has made so
>>> far. By "system" I guess I mean a person in charge of
>>> recording such information or perhaps a table somewhere to
>>> consult. But if it's less formal than all that, I suppose
>>> I'll just rely on the git history and whatever an author
>>> self-reports. Thanks.
>>
>> No, we don't have such a system, unfortunately.
>> It's somewhat subjective what counts -- we try to count
>> "lines of code", so whitespace changes don't count, of
>> course, and other trivial transforms don't count either.
>
> 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.
I've seen a git command do something similar for the Emacs
source ... posted on gmane.emacs.help not so long ago.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-01-31 3:30 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r18oa8fd.fsf@zoho.eu \
--to=emacs-erc@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.