git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git as an sfc member project
Date: Fri, 26 Feb 2010 16:56:44 +0100	[thread overview]
Message-ID: <201002261656.47740.jnareb@gmail.com> (raw)
In-Reply-To: <20100226123945.GD10198@coredump.intra.peff.net>

On Fri, 26 Feb 2010, Jeff King wrote:
> On Wed, Feb 24, 2010 at 08:07:13AM -0800, Jakub Narebski wrote:
> 
> > > [This is basically "shortlog -ns | head". I am happy to make it shorter
> > > or longer if people think it should be. Affiliations?]
> > 
> > I wouldn't say I am "key developer"...
> 
> Well, you have a lot of commits, anyway. ;)

Well, there are mainly (310 out of 398 in whole lifetime of git) about
gitweb, which is rather disconnected subsystem of git, started by
Kay Sievers.

> > In the "A note from maintainer", which is send periodically to git
> > mailing list, and which is also available as MaintNotes file in 'todo'
> > branch in git repository, you have the following description of
> > developers at the end of this file:
> 
> Yeah, I thought about that list, but it is very long. Honestly even
> putting ten people on the list seems long to me. I think git has a very
> different distribution of committers than many other projects.

Well, it at least lists contributors by subsystem...

-- 
Jakub Narebski
Poland

  reply	other threads:[~2010-02-26 15:57 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 [this message]
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
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=201002261656.47740.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --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).