git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Jon Smirl" <jonsmirl@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: New mailmap file for the kernel
Date: Mon, 28 Jul 2008 13:53:08 +0200	[thread overview]
Message-ID: <bd6139dc0807280453rbfc28ffid8314e74cc19b7f7@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807281321540.2725@eeepc-johanness>

On Mon, Jul 28, 2008 at 13:23, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> And how exactly do you plan to make sure everybody has that hook
> installed?

It needn't be installed with everybody, only at the people that form
'upstream' (in the git case that'd be Junio, in the Linux case that'd
be Linus and his lieutenants).

> Also, it would be a major hassle, just for the benefits of statistics
> (which, funnily enough, not everybody cares about).

Hmmm, I'm not sure if it would be a major hassle once it's set up?
Once everybody has their name correctly in the mailmap nobody will
have to care?

> But we are not truly distributed.  Our community is small enough, and our
> maintainer good enough, that we do have a single upstream essentially.  We
> do not even have lieutenants through which new developers could come (and
> therefore would be old developers once they hit master).

Ah, I did not realize that. Thanks for explaining.

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2008-07-28 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28  4:45 New mailmap file for the kernel Jon Smirl
2008-07-28 10:53 ` Johannes Schindelin
2008-07-28 11:11   ` Sverre Rabbelier
2008-07-28 11:23     ` Johannes Schindelin
2008-07-28 11:53       ` Sverre Rabbelier [this message]
2008-07-28 12:47         ` Jon Smirl

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=bd6139dc0807280453rbfc28ffid8314e74cc19b7f7@mail.gmail.com \
    --to=alturin@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    --cc=sverre@rabbelier.nl \
    /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).