From: Marius Storm-Olsen <marius@trolltech.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Extend mailmap functionality
Date: Mon, 02 Feb 2009 09:07:42 +0100 [thread overview]
Message-ID: <4986A9CE.9040009@trolltech.com> (raw)
In-Reply-To: <7vpri1o801.fsf@gitster.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]
Junio C Hamano said the following on 02.02.2009 04:03:
>> This extended mapping is necessary when a company wants to have
>> their repositories open to the public, but needs to protect the
>> identities of the developers. It enables you to only show nicks
>> and standardized emails, like 'Dev123 <bugs@company.xx>' in the
>> public repo, but by using an private mailmap file, map the name
>> back to 'John Doe <john.doe@company.xx>' inside the company.
>
> I do not find the "necessary" argument very convincing nor I find
> the particular use case sane. You may want to do things that way,
> but I do not know if it is the best way to go about it.
Well, this is the use-case for my company. We have open-source repos,
which are the exact same repos which the company's developers work on,
not a modified mirror repo.
However, laws in some countries requires that employees information be
kept away from the public, should they so wish. So, for our developers
to work on the exact same repo as the open-source community, we need a
way to map both Names and Emails back to the original author, inside
the company without using a different repo.
Also, the company commit policy might be such that the email on the
commit is always the companys <bugs@company.xx>. This might be so that
if someone finds a bug to your commit, they send the bug report to the
companys bug-tracker instead of the individual email address.
However, that breaks the old mailmap system, since it requires unique
email addresses to map to a name.
> The new mapping however brings in more flexibility, and there may
> be other use cases where people benefit from that flexibility. I
> am slightly in favor than neutral to this new feature.
You could use this feature in git.git itself, where for example
Junio C Hamano <gitster@pobox.com>
Junio C Hamano <gitster@pobox.com> <junio@twinsun.com>
(or any of the others in the .mailmap file with X number of different
email addresses), to ensure that you are always associated with one
specific email address.
--
.marius [@trolltech.com]
'if you know what you're doing, it's not research'
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
prev parent reply other threads:[~2009-02-02 8:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 20:59 [PATCH v2 0/4] Extend mailmap functionality Marius Storm-Olsen
2009-02-01 20:59 ` [PATCH v2 1/4] Add log.mailmap as configurational option for mailmap location Marius Storm-Olsen
2009-02-01 20:59 ` [PATCH v2 2/4] Add find_insert_index, insert_at_index and clear_func functions to string_list Marius Storm-Olsen
2009-02-01 20:59 ` [PATCH v2 3/4] Add map_user() and clear_mailmap() to mailmap Marius Storm-Olsen
2009-02-01 20:59 ` [PATCH v2 4/4] Change current mailmap usage to do matching on both name and email of author/committer Marius Storm-Olsen
2009-02-02 3:03 ` [PATCH v2 2/4] Add find_insert_index, insert_at_index and clear_func functions to string_list Junio C Hamano
2009-02-02 7:49 ` Marius Storm-Olsen
2009-02-02 3:01 ` [PATCH v2 1/4] Add log.mailmap as configurational option for mailmap location Junio C Hamano
2009-02-02 7:48 ` Marius Storm-Olsen
2009-02-02 7:56 ` Junio C Hamano
2009-02-02 8:26 ` Marius Storm-Olsen
2009-02-02 8:40 ` Junio C Hamano
2009-02-02 3:03 ` [PATCH v2 0/4] Extend mailmap functionality Junio C Hamano
2009-02-02 5:26 ` Sverre Rabbelier
2009-02-02 8:07 ` Marius Storm-Olsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4986A9CE.9040009@trolltech.com \
--to=marius@trolltech.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).