From: Christian Couder <chriscool@tuxfamily.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git as an sfc member project
Date: Wed, 24 Feb 2010 18:44:37 +0100 [thread overview]
Message-ID: <201002241844.37207.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20100224154452.GA25872@coredump.intra.peff.net>
On Wednesday 24 February 2010 16:44:53 Jeff King wrote:
> A while back I mentioned that we had some leftover GSoC money, and
> suggested joining the Software Freedom Conservancy as a member project:
>
> http://article.gmane.org/gmane.comp.version-control.git/134435
>
> People seemed to think it was a good idea, so I have gone in that
> direction.
Thanks for that!
> > * Names, email addresses, and affiliations of key developers, past and
> > present.
>
> Junio C Hamano <gitster@pobox.com>
> Shawn O. Pearce <spearce@spearce.org>
> Linus Torvalds <torvalds@linux-foundation.org>
> Johannes Schindelin <Johannes.Schindelin@gmx.de>
> Eric Wong <normalperson@yhbt.net>
> Jeff King <peff@peff.net>
> Jakub Narebski <jnareb@gmail.com>
> Nicolas Pitre <nico@fluxnic.net>
> Paul Mackerras <paulus@samba.org>
> Christian Couder <chriscool@tuxfamily.org>
I am very happy to be considered a key developer in your list, but it seems
unfair for both Johannes Sixt and Simon Hausmann as they have a higher commit
count than I have. So you should perhaps add them too. Or did you count lines
of code?
> [This is basically "shortlog -ns | head". I am happy to make it shorter
> or longer if people think it should be. Affiliations?]
About affiliations, I did practically all of my work on Git at home during my
free time, so I have none. But I would happy to have one in the future, if
some company would be willing to pay me for working on Git or Git related stuff
(hint, hint! ;-)
Thanks,
Christian.
next prev parent reply other threads:[~2010-02-24 17:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 15:44 git as an sfc member project Jeff King
2010-02-24 16:07 ` Jakub Narebski
2010-02-26 12:39 ` Jeff King
2010-02-26 15:56 ` Jakub Narebski
2010-03-01 10:58 ` Jeff King
2010-02-24 16:22 ` Shawn O. Pearce
2010-02-26 12:49 ` Jeff King
2010-02-24 17:44 ` Christian Couder [this message]
2010-02-26 12:25 ` Jeff King
2010-02-24 18:12 ` Junio C Hamano
2010-02-26 12:29 ` Jeff King
2010-02-26 12:37 ` Jeff King
2010-02-26 12:59 ` Jeff King
2010-02-26 13:14 ` Julian Phillips
2010-03-01 10:53 ` Jeff King
2010-02-27 6:35 ` Eric Wong
-- strict thread matches above, loose matches on Subject: below --
2010-10-22 18:30 Jeff King
2010-10-22 19:19 ` Shawn Pearce
2010-10-22 19:35 ` Jeff King
2010-10-22 20:06 ` Shawn Pearce
2010-10-22 20:59 ` Sverre Rabbelier
2010-10-22 21:48 ` Junio C Hamano
2010-10-22 22:59 ` Junio C Hamano
2010-10-22 23:18 ` Jeff King
2010-10-22 23:21 ` Brandon Casey
2010-10-22 23:26 ` Junio C Hamano
[not found] ` <hh0bQq8TcM0saDTuJo6qVdOMgn-14aysvhF_S70syB678Of7zQOsY9jLajG2WpeGXid8jtG4kVA@cipher.nrlssc.navy.mil>
2010-10-23 0:09 ` Brandon Casey
2010-10-23 1:30 ` Brandon Casey
2010-10-23 22:48 ` Brandon Casey
2010-10-22 23:22 ` Junio C Hamano
2010-10-23 11:52 ` Ævar Arnfjörð Bjarmason
2010-10-23 13:39 ` Jeff King
2010-10-23 16:03 ` A Large Angry SCM
2010-10-26 22:39 ` Jeff King
2010-10-27 7:03 ` Tait
2010-10-27 11:08 ` Jeff King
2010-11-02 23:03 ` Bradley M. Kuhn
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=201002241844.37207.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).