GNU bug report logs - #53617
28.0.90; duplicate checks in erc--switch-to-buffer

Previous Next

Full log

Message #40 received at 53617 <at> debbugs.gnu.org (full text, mbox):

From: Michael Olson <mwolson <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: emacs-erc <at> gnu.org, bandali <at> gnu.org, "J.P." <jp <at> neverwas.me>,
 53617 <at> debbugs.gnu.org, strings.stringsandstrings <at> gmail.com,
 Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#53617: 28.0.90; duplicate checks in erc--switch-to-buffer
Date: Sun, 30 Jan 2022 22:22:05 -0500

[Message part 1 (text/plain, inline)]

On Sun, Jan 30, 2022 at 11:00 AM Lars Ingebrigtsen <larsi <at> gnus.org> wrote:

> "J.P." <jp <at> neverwas.me> writes:
>
> > 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.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.