All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <stefanbeller@gmail.com>
Cc: git@vger.kernel.org, Stefan Beller <sbeller@google.com>
Subject: Re: [PATCH 2/2] .mailmap: Add Stefan Bellers corporate mail address
Date: Mon, 20 Oct 2014 22:53:33 -0700	[thread overview]
Message-ID: <xmqqppdm0y02.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1413856245-5443-2-git-send-email-stefanbeller@gmail.com> (Stefan Beller's message of "Mon, 20 Oct 2014 18:50:45 -0700")

Stefan Beller <stefanbeller@gmail.com> writes:

> From: Stefan Beller <sbeller@google.com>
>
> Note that despite the private address being first, Google owns the
> copyright on this patch as any other patch I'll be sending signed off
> by the sbeller@google.com address.

While Googlers are encouraged to interact with external open source
projects using their corp address when working as new contributors,
Googlers are also encouraged to keep using the same pre-corp address
when working with projects they have been part of for continuity.

After all, even if you send patches from your @gmail.com address
while being employed by Google, the patches are copyright Google,
not yours, and DCO (a) "I have the right to submit" covers your
submissions just fine (i.e. it does not say "I own the copyright"),
as long as you are cleared to contribute your patches to us by
Google's open source office (which I happen to know that you have
already done).

The mailmap is primarily to correct past mistakes and document the
new addresses of those who lost the old address to maintain their
reachability.  It is not about planning to send patches from two
different addresses chosen by the phase of the moon or something.

I do not terribly mind, but is this patch really necessary?

>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
>  .mailmap | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/.mailmap b/.mailmap
> index 8aefb5a..bb6f52e 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -205,6 +205,7 @@ Shawn O. Pearce <spearce@spearce.org>
>  Simon Hausmann <hausmann@kde.org> <simon@lst.de>
>  Simon Hausmann <hausmann@kde.org> <shausman@trolltech.com>
>  Stefan Beller <stefanbeller@gmail.com> <stefanbeller@googlemail.com>
> +Stefan Beller <stefanbeller@gmail.com> <sbeller@google.com>
>  Stefan Naewe <stefan.naewe@gmail.com> <stefan.naewe@atlas-elektronik.com>
>  Stefan Naewe <stefan.naewe@gmail.com> <stefan.naewe@googlemail.com>
>  Stefan Sperling <stsp@elego.de> <stsp@stsp.name>

  reply	other threads:[~2014-10-21  5:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  1:50 [PATCH 1/2] transport: Free leaking head in transport_print_push_status Stefan Beller
2014-10-21  1:50 ` [PATCH 2/2] .mailmap: Add Stefan Bellers corporate mail address Stefan Beller
2014-10-21  5:53   ` Junio C Hamano [this message]
     [not found]     ` <CAGZ79kYNvQOKLZ5qgCD1NyYG8X2q7UCr5rMbrxW6ajRAnFRz7A@mail.gmail.com>
2014-10-22 22:03       ` Junio C Hamano

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=xmqqppdm0y02.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.com \
    --cc=stefanbeller@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.