All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] docs: reminder to not expose potentially private email addresses
Date: Sat, 16 Nov 2024 10:33:57 +0100	[thread overview]
Message-ID: <cover.1731749544.git.linux@leemhuis.info> (raw)

Remind developers to not expose private email addresses, as some people
become upset if their addresses end up in the lore archives or the Linux
git tree -- especially when it comes to bugzilla.kernel.org.

This fixes a few issues along the way that came up during preparation or
review of the change.

Ciao, Thorsten

---
v2:
- Intial version starting with "2", as the second patch was posted
  before.

Thorsten Leemhuis (2):
  docs: 5.Posting: mentioned Suggested-by: tag
  docs: clarify rules wrt tagging other people

 Documentation/process/5.Posting.rst          | 21 ++++++++--
 Documentation/process/submitting-patches.rst | 44 ++++++++++++++------
 2 files changed, 49 insertions(+), 16 deletions(-)


base-commit: 623e5747c680d3854b6b9882d9907096bc63580d
-- 
2.45.0


             reply	other threads:[~2024-11-16  9:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16  9:33 Thorsten Leemhuis [this message]
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
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=cover.1731749544.git.linux@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.