all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: Getting email addresses obfuscated in patch attachments created by "git format-patch"
Date: Wed, 17 May 2023 05:31:06 +0300	[thread overview]
Message-ID: <83zg63y9hx.fsf@gnu.org> (raw)
In-Reply-To: <e6e4dc61-0bb9-584d-dbfb-9d17036fbea9@vodafonemail.de> (message from Jens Schmidt on Tue, 16 May 2023 22:17:06 +0200)

> Date: Tue, 16 May 2023 22:17:06 +0200
> Cc: philipk@posteo.net, emacs-devel@gnu.org
> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> 
> On 2023-05-16  20:57, Eli Zaretskii wrote:
> 
> > I'm not sure you can conceal your email address in practice if you
> > contribute changes to Emacs (or to any other projects with a public
> > repository).  That's because anyone could see your email address by
> > just walking the commit logs.  And many projects, Emacs included, have
> > a special mailing list where each commit is automatically posted, with
> > all its information, so anyone accessing the archives of such a list
> > will also see the email addresses of the contributors, and crawlers
> > can pick them up.
> > 
> > Thus, I'm not sure why you should insist on obfuscating the email
> > address in just those patches, since it will be visible in other
> > places anyway.
> 
> Ah.  So even if I supply a patch to Emacs by email, and someone else 
> merges it, I will occur as commit author in git?

Yes.  We take correct attribution seriously, so you should always be
the Author of the commits that install changes written by you.



      reply	other threads:[~2023-05-17  2:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 21:43 Getting email addresses obfuscated in patch attachments created by "git format-patch" Jens Schmidt
2023-05-16  6:46 ` Philip Kaludercic
2023-05-16 18:31   ` Jens Schmidt
2023-05-16 18:57     ` Eli Zaretskii
2023-05-16 20:17       ` Jens Schmidt
2023-05-17  2:31         ` Eli Zaretskii [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=83zg63y9hx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jschmidt4gnu@vodafonemail.de \
    --cc=philipk@posteo.net \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.