From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH v2 2/2] docs: clarify rules wrt tagging other people
Date: Sat, 16 Nov 2024 12:38:23 +0100 [thread overview]
Message-ID: <CAMuHMdU5fsLDvwf6-cQhvpNB_7e+KZRrqj1UOMz7YjXRv0cZTg@mail.gmail.com> (raw)
In-Reply-To: <b7dce8b22a391c2f8f0d5a47bf23bc852eca4e71.1731749544.git.linux@leemhuis.info>
Hi Thorsten,
On Sat, Nov 16, 2024 at 10:39 AM Thorsten Leemhuis <linux@leemhuis.info> wrote:
> The latter is not a theoretical issue, as one maintainer mentioned that
> his employer received a EU GDPR (general data protection regulation)
> complaint after exposing a email address used in bugzilla through a tag
> in a patch description.
And once it's upstream there is not much we can do about that anymore,
right?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-11-16 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 9:33 [PATCH v2 0/2] docs: reminder to not expose potentially private email addresses Thorsten Leemhuis
2024-11-16 9:33 ` [PATCH v2 1/2] docs: 5.Posting: mentioned Suggested-by: tag Thorsten Leemhuis
2024-11-16 10:39 ` Greg KH
2024-11-16 9:33 ` [PATCH v2 2/2] docs: clarify rules wrt tagging other people Thorsten Leemhuis
2024-11-16 10:42 ` Greg KH
2024-11-16 11:07 ` Thorsten Leemhuis
2024-11-16 11:50 ` Mauro Carvalho Chehab
2024-11-16 12:27 ` Thorsten Leemhuis
2024-11-16 13:16 ` Mauro Carvalho Chehab
2024-11-16 11:38 ` Geert Uytterhoeven [this message]
2024-11-16 11:51 ` Thorsten Leemhuis
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=CAMuHMdU5fsLDvwf6-cQhvpNB_7e+KZRrqj1UOMz7YjXRv0cZTg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=corbet@lwn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mchehab+huawei@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=workflows@vger.kernel.org \
/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