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:11:13 +0200 [thread overview]
Message-ID: <bd6139dc0807280411k3a283c5dr4b874342aab167dc@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807281251000.2725@eeepc-johanness>
On Mon, Jul 28, 2008 at 12:53, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Unless somebody forgets, right?
Unless there is a pre-commit hook that prevents you from committing
when you are not in the mailmap. That should give enough incentive to
first make a commit that puts you in the mailmap before you start
sending in patches.
> Also note that in a distributed world, you cannot properly speak of a "new
> developer".
Yet we do it all the time on git.git ;).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-07-28 11:12 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 [this message]
2008-07-28 11:23 ` Johannes Schindelin
2008-07-28 11:53 ` Sverre Rabbelier
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=bd6139dc0807280411k3a283c5dr4b874342aab167dc@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).