From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Olson Newsgroups: gmane.emacs.bugs,gmane.emacs.erc.general Subject: bug#53617: 28.0.90; duplicate checks in erc--switch-to-buffer Date: Sun, 30 Jan 2022 22:22:05 -0500 Message-ID: References: <87ee4rutmo.fsf@neverwas.me> <871r0rusl5.fsf@neverwas.me> <878ruyqf0b.fsf@neverwas.me> <83a6fdbulb.fsf@gnu.org> <878rux9ql2.fsf@neverwas.me> <87bkztb4di.fsf@gnus.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a1c10d05d6d84ada" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27312"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-erc@gnu.org, bandali@gnu.org, "J.P." , 53617@debbugs.gnu.org, strings.stringsandstrings@gmail.com To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 31 04:23:31 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nENHu-0006uE-1X for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 31 Jan 2022 04:23:30 +0100 Original-Received: from localhost ([::1]:48358 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nENHs-0007nX-I8 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 30 Jan 2022 22:23:28 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:34878) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nENHS-0007nO-1A for bug-gnu-emacs@gnu.org; Sun, 30 Jan 2022 22:23:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45199) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nENHR-0007El-O7 for bug-gnu-emacs@gnu.org; Sun, 30 Jan 2022 22:23:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nENHR-0006oY-Jp for bug-gnu-emacs@gnu.org; Sun, 30 Jan 2022 22:23:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Michael Olson Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 31 Jan 2022 03:23:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53617 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 53617-submit@debbugs.gnu.org id=B53617.164359934426141 (code B ref 53617); Mon, 31 Jan 2022 03:23:01 +0000 Original-Received: (at 53617) by debbugs.gnu.org; 31 Jan 2022 03:22:24 +0000 Original-Received: from localhost ([127.0.0.1]:38102 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nENGq-0006nZ-Fl for submit@debbugs.gnu.org; Sun, 30 Jan 2022 22:22:24 -0500 Original-Received: from mail-ej1-f42.google.com ([209.85.218.42]:45722) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nENGo-0006nJ-Mf for 53617@debbugs.gnu.org; Sun, 30 Jan 2022 22:22:23 -0500 Original-Received: by mail-ej1-f42.google.com with SMTP id me13so38448690ejb.12 for <53617@debbugs.gnu.org>; Sun, 30 Jan 2022 19:22:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FgNzkWXK1mJA9+hfq9uAevMYt83xXOGrO55M9LMZlpo=; b=rR6ZdP+05zZ4DYMCQbX1OCzqkY9n31uyGl4uMdO9eYWIEZPwxSRzvzsNQ9d4k23yvr VfMKtiw6fJwW9+0dN/HplhmNyfjZKSntwINmUPK5ir5S2tp2ZyXh36pY2UYk7XBHX+UP SQP3Jc00CRGuq+7Ggal124lQGPu9yiWhWTXdYJ95rl5fVa7e8fJD59TdSK/za3yp1Vj7 ZaB1GGfd/JXxWZpWzW7BhbPqP6LiVdLmnXDiQZtFiUH7W+gETFQUEnMjSifACN4q7U+T qXtQ5H56ilkimvkaC3fA1XG0HsdsKkeVWYkmM2JbkQsu28rNvfcmEbfR8bZSnGQ/2bN8 ErOg== X-Gm-Message-State: AOAM532qPIbxGJlDyZ/KMfwzReve3j1v+DcGuy24zuOHIutn9saynVxJ enAe5WDN5AV8O1f1da9ECpYTYzLyagRg4yaBtvIsAw== X-Google-Smtp-Source: ABdhPJy0OH7vLNSwgbraTNP0AYg596rUH7VEklctePm9g0qMnXFJTPmHtJZsY+OwosRJfShEzpqS12tLuNgUQN085yg= X-Received: by 2002:a17:907:7289:: with SMTP id dt9mr16290052ejc.62.1643599336942; Sun, 30 Jan 2022 19:22:16 -0800 (PST) In-Reply-To: <87bkztb4di.fsf@gnus.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:225651 gmane.emacs.erc.general:1717 Archived-At: --000000000000a1c10d05d6d84ada Content-Type: text/plain; charset="UTF-8" On Sun, Jan 30, 2022 at 11:00 AM Lars Ingebrigtsen wrote: > "J.P." 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. --000000000000a1c10d05d6d84ada Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Jan 30, 2022 at 11:00 AM Lars Ing= ebrigtsen <larsi@gnus.org> wrot= e:
"J.P." <jp@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 s= o
> far. By "system" I guess I mean a person in charge of record= ing such
> information or perhaps a table somewhere to consult. But if it's l= ess
> 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.=C2=A0 It's somewhat=
subjective what counts -- we try to count "lines of code", so whi= tespace
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, a= nd (in the case of unassigned contributors) how many lines so I knew if the= y 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.
--000000000000a1c10d05d6d84ada--