emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: [OT] Contributors to org.texi (was: GFDL)
Date: Tue, 21 May 2013 16:12:51 +0000 (UTC)	[thread overview]
Message-ID: <87hahwjq9n.fsf@mean.albasani.net> (raw)
In-Reply-To: 86ppwkij9r.fsf@somewhere.org

"Sebastien Vauban" <sva-news@mygooglest.com>
writes:

> Bastien wrote:
>> Well, relicensing the Org compact guide under GNU GPL is definitely
>> feasible, but relicensing the Org manual is (sadly) not.  Let's take
>> the feasible step first?
>
> FMI, why is GNU GPL not applicable to the manual?

Hehe, on an unrelated side note, that made me curious: 
Who did actually end up in org.texi, and how would I start to find out?

0. $ git blame -C -C -M -e org.texi > ~/git-blame.txt
   (I searched the web for that ;)
1. We are only interested in the email addresses, so quick clean up with
   a keyboard macro.
2. Get rid of duplicates: 
   M-x sort-lines
   C-x h 
   M-x shell-command-on-region 
   uniq

And... I see 67 different addresses. Some clearly belong to one person,
so getting rid of the obvious ones my count goes down to ... 58?

Wow... 
Fun.

Back to work :)

Memon

      parent reply	other threads:[~2013-05-21 16:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 14:30 GFDL Carsten Dominik
2013-03-09 15:02 ` GFDL Achim Gratz
2013-03-09 15:11   ` GFDL Carsten Dominik
2013-03-09 15:25     ` GFDL Achim Gratz
2013-03-09 16:13       ` GFDL Carsten Dominik
2013-03-10 10:07         ` GFDL Bastien
2013-03-10 12:31           ` GFDL Achim Gratz
2013-03-10 14:06             ` GFDL Bastien
2013-03-10  0:43     ` GFDL Alan L Tyree
2013-03-19  6:44       ` GFDL Carsten Dominik
2013-03-19 15:42         ` GFDL Bastien
2013-03-19 19:06         ` GFDL Marcin Borkowski
2013-03-19 21:35           ` GFDL Bastien
2013-03-20  2:56             ` GFDL Marcin Borkowski
2013-03-20  6:01               ` GFDL Marcin Borkowski
2013-03-20 14:00                 ` GFDL Bastien
2013-03-20 15:25                   ` GFDL Marcin Borkowski
2013-03-20 19:55                     ` GFDL Marcin Borkowski
2013-04-06  1:05                       ` GFDL Bastien
2013-05-21  1:02         ` GFDL Ben Finney
2013-05-21 10:27           ` GFDL Bastien
2013-05-21 12:56             ` GFDL Sebastien Vauban
2013-05-21 13:01               ` GFDL Bastien
2013-05-26  3:35                 ` GFDL Ben Finney
2013-05-27  7:12                   ` GFDL Bastien
2013-06-04  9:35                     ` GFDL Ben Finney
2013-05-21 13:34               ` GFDL François Pinard
2013-05-21 14:18                 ` GFDL Carsten Dominik
2013-05-21 15:03                   ` GFDL François Pinard
2013-05-22  4:43                     ` GFDL Carsten Dominik
2013-05-21 16:12               ` Memnon Anon [this message]

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hahwjq9n.fsf@mean.albasani.net \
    --to=gegendosenfleisch@googlemail.com \
    --cc=emacs-orgmode@gnu.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/org-mode.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).