From: Andreas Ericsson <ae@op5.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: git to libgit2 code relicensing
Date: Fri, 14 Nov 2008 21:59:56 +0100 [thread overview]
Message-ID: <491DE6CC.6060201@op5.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
I've been working quite a lot on git -> libgit2 code moving,
but the licensing stuff is a bit depressing, as I can't know
if the work I'm doing is for nothing or not.
The license decided for libgit2 is "GPL with gcc exception".
Those who are OK with relicensing their contributions under
that license for the purpose of libgit2, can you please say
so?
I'm planning on writing a tool for this that will have "ok",
"not ok" and "ask-each-patch" as options.
The list of people whose position I know is rather short.
Please correct me if you're on it and would like not to be.
Junio C. Hamano ask
Johannes Schindelin ok
Shawn O. Pearce ok
Andreas Ericsson ok
Pierre Habouzit ok
Brian Gernhardt ok
I've put everyone who "owns" more than 500 lines of code
on the bcc list, figuring your permission is important
but that you don't want the hundreds (well, one can hope)
of emails from people saying "ok". The list of major owners
was generated with "git showners *.c" in a worktree from
the next branch of git.git.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
[-- Attachment #2: git-showners --]
[-- Type: text/plain, Size: 673 bytes --]
#!/bin/sh
test "$#" -gt 0 || { echo "Usage: $0 <file>"; exit 1; }
combined=t
while test "$#" -gt 0
do
case "$1" in
-c|--combined)
combined=t
;;
-i|--individual)
combined=
;;
--)
shift
break
;;
*)
break
;;
esac
shift
done
sort_enumerate ()
{
sed -e 's/[^(]*(\([^0-9]*\).*/\1/' -e 's/[\t ]*$//' \
| sort | uniq -c | sort -nr
}
show_owners ()
{
for f in "$@"; do
test -d "$f" && { show_owners "$f"/*; continue; }
git blame -C -C -M "$f"
done
}
if test "$combined" = t; then
echo "$@"
show_owners "$@" | sort_enumerate
else
echo "Showing one-at-a-time ownership"
for f in "$@"; do
echo "$f"
show_owners "$f" | sort_enumerate
done
fi
next reply other threads:[~2008-11-14 21:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 20:59 Andreas Ericsson [this message]
2008-11-14 21:33 ` git to libgit2 code relicensing Martin Koegler
2008-11-14 21:46 ` Sverre Rabbelier
2008-11-14 22:57 ` Andreas Ericsson
2008-11-14 22:56 ` Andreas Ericsson
2008-11-15 17:13 ` Martin Koegler
2008-11-14 23:13 ` Linus Torvalds
2008-11-14 23:46 ` Shawn O. Pearce
2008-11-15 4:30 ` David Brown
2008-11-15 5:00 ` Shawn O. Pearce
2008-11-15 8:04 ` Nicolas Pitre
2008-11-15 18:39 ` David Brown
2008-11-15 12:39 ` Miklos Vajna
2008-11-15 13:00 ` Junio C Hamano
2008-11-15 19:33 ` Miklos Vajna
2008-11-15 22:12 ` Pierre Habouzit
2008-11-15 18:49 ` David Brown
2008-11-15 16:39 ` Linus Torvalds
2008-11-15 10:17 ` Andreas Ericsson
2008-11-15 10:28 ` Pau Garcia i Quiles
2008-11-15 11:05 ` Andreas Ericsson
2008-11-15 11:33 ` Pau Garcia i Quiles
2008-11-15 11:52 ` Andreas Ericsson
2008-11-15 18:53 ` David Brown
2008-11-16 1:30 ` Daniel Barkalow
[not found] ` <200811151615.42345.chriscool@tuxfamily.org>
2008-11-16 11:50 ` Andreas Ericsson
2008-11-16 21:00 ` Johannes Schindelin
2008-11-16 21:09 ` Sverre Rabbelier
2008-11-17 7:24 ` Andreas Ericsson
2008-11-17 15:40 ` Shawn O. Pearce
2008-11-17 21:44 ` Andreas Ericsson
2008-11-20 17:41 ` René Scharfe
2008-11-25 15:19 ` Kristian Høgsberg
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=491DE6CC.6060201@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).