git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: "Mike.lifeguard" <mike.lifeguard@gmail.com>,
	Theodore Tso <tytso@MIT.EDU>,
	git@vger.kernel.org
Subject: Re: Pseudonymous commits
Date: Thu, 25 Mar 2010 16:57:22 -0700 (PDT)	[thread overview]
Message-ID: <m34ok4j6qi.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.1003251459540.694@xanadu.home>

Nicolas Pitre <nico@fluxnic.net> writes:

> On Thu, 25 Mar 2010, Mike.lifeguard wrote:
> 
> > On 10-03-25 01:39 AM, Theodore Tso wrote:
> > > How do you know whether said contributor
> > > isn't a Chinese intelligence agent trying to insert a backdoor into
> > > your program
> > 
> > Because they are only contributing translations.
> 
> Just take over authorship of the patch yourself then.
> 
> Or pick a generic email address such as the translator's mailing list 
> email address or the like.

In the case of translations one cal use generic "language team"
mailing list, i.e. <LL@li.org> (where LL is ISO code of language,
e.g. 'de@li.org' for translations to German, etc.).

-- 
Jakub Narebski
Poland
ShadeHawk on #git

      parent reply	other threads:[~2010-03-26  0:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  3:57 Pseudonymous commits Mike.lifeguard
2010-03-25  4:39 ` Theodore Tso
2010-03-25  4:41   ` Mike.lifeguard
2010-03-25  4:54     ` Kris Shannon
2010-03-25  5:00       ` Mike.lifeguard
2010-03-25  5:14         ` Avery Pennarun
2010-03-25  9:18         ` Alex Riesen
2010-03-25 11:05         ` Santi Béjar
2010-03-25 19:02     ` Nicolas Pitre
2010-03-25 19:26       ` Mike.lifeguard
2010-03-25 20:14         ` Nicolas Pitre
2010-03-25 21:30           ` Chris Packham
2010-03-25 23:57       ` Jakub Narebski [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=m34ok4j6qi.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mike.lifeguard@gmail.com \
    --cc=nico@fluxnic.net \
    --cc=tytso@MIT.EDU \
    /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).