unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Guy Gastineau <strings.stringsandstrings@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-erc@gnu.org, bandali@gnu.org, 53617@debbugs.gnu.org,
	"J.P." <jp@neverwas.me>
Subject: bug#53617: 28.0.90; duplicate checks in erc--switch-to-buffer
Date: Sun, 30 Jan 2022 11:25:05 -0500	[thread overview]
Message-ID: <CAHgGP-JDd8P+4-J63Hk4ymHkYpH_JcbQgKEtiAmKyNoPT09WzA__40773.5726841324$1643560016$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <87bkztb4di.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Yeah, I have no problem with the copyright assignment.  I will look in the
docs to see what I need to give you all for it.

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

> "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 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.
>
> So as you say -- you just have to look at the commit history and make a
> judgement call in these cases.  (Or even better, ask for a copyright
> assignment form and then you don't have to count. 😀)
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: Type: text/html, Size: 1842 bytes --]

  parent reply	other threads:[~2022-01-30 16: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
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 [this message]
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-JDd8P+4-J63Hk4ymHkYpH_JcbQgKEtiAmKyNoPT09WzA__40773.5726841324$1643560016$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).