From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pkgcore/snakeoil:master commit in: /
Date: Thu, 25 Jan 2024 15:41:44 +0000 (UTC) [thread overview]
Message-ID: <1706155346.44908721de14029c4ebe3ae12d0058381e8343d6.arthurzam@gentoo> (raw)
commit: 44908721de14029c4ebe3ae12d0058381e8343d6
Author: Brian Harring <ferringb <AT> gmail <DOT> com>
AuthorDate: Thu Jan 25 04:01:03 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 25 04:02:26 2024 +0000
URL: https://gitweb.gentoo.org/proj/pkgcore/snakeoil.git/commit/?id=44908721
authors: Add myself to the list.
While I'm at it, I pulled the current *rough* breakdown
of who owns what copyright; per the other commits in
the pkgcore ecosystem, this is primarily to ensure folks
get called out, and to also give a touchpoint should there
ever again need to be a license change (which requires all
owners to sign off on it, something that was done for gpl2 -> bsd).
Current list:
```
ferringb@frith ~/gentoo/snakeoil $ git ls-files | xargs -n1 git blame -ew | cut -d\< -f2 | cut -d@ -f1 | sort -g | uniq -c | sort -gr
10393 ferringb
8536 radhermit
1409 arthurzam
171 sam
114 mgorny
73 vapier
21 marien.zwart
```
Vapier/Spanky was pylint changes, sam/mgorny can add themselves when they
feel appropriate.
Marienz actually created the formatter classes and had involvement in tests,
although I can't state how much is there but my recollection is outside of formatters,
nothing but one off bug fixes. For better or worse, snakeoil was my creation and
ownership of some of that metaprogramming crazyness in use.
If there was anyone overlooked (due to VCS historical issues) or neglected,
apologies in advance. Per other commits, >15 years, etc, etc, etc.
Signed-off-by: Brian Harring <ferringb <AT> gmail.com>
pyproject.toml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/pyproject.toml b/pyproject.toml
index 0baf0228..4e951399 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -7,9 +7,11 @@ name = "snakeoil"
description = "misc common functionality and useful optimizations"
readme = "README.rst"
requires-python = "~=3.10"
+# alphabetical by surname
authors = [
- {name = "Tim Harder", email = "radhermit@gmail.com"},
- {name = "Arthur Zamarin", email = "arthurzam@gentoo.org"},
+ {name = "Tim Harder", email = "radhermit@gmail.com"},
+ {name = "Brian Harring", email = "ferringb@gmail.com"},
+ {name = "Arthur Zamarin", email = "arthurzam@gentoo.org"},
]
maintainers = [
{name = "Arthur Zamarin", email = "arthurzam@gentoo.org"},
next reply other threads:[~2024-01-25 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 15:41 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-08 19:43 [gentoo-commits] proj/pkgcore/snakeoil:master commit in: / Arthur Zamarin
2024-01-26 19:50 Arthur Zamarin
2024-01-26 9:19 Arthur Zamarin
2024-01-25 15:41 Arthur Zamarin
2024-01-19 9:59 Arthur Zamarin
2023-12-22 15:04 Arthur Zamarin
2023-12-22 14:59 Arthur Zamarin
2023-03-24 10:55 Arthur Zamarin
2022-12-25 18:20 Arthur Zamarin
2022-12-25 18:11 Arthur Zamarin
2022-12-25 17:49 Arthur Zamarin
2022-12-09 13:50 Arthur Zamarin
2022-11-15 6:24 Arthur Zamarin
2022-11-08 19:22 Arthur Zamarin
2022-11-08 18:38 Arthur Zamarin
2022-11-08 18:38 Arthur Zamarin
2022-11-02 18:53 Arthur Zamarin
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=1706155346.44908721de14029c4ebe3ae12d0058381e8343d6.arthurzam@gentoo \
--to=arthurzam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox