public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH BlueZ] Fix URL for submitting patches
@ 2025-03-10 10:41 Andrew Sayers
  2025-03-10 12:04 ` [BlueZ] " bluez.test.bot
  2025-03-12 16:50 ` [PATCH BlueZ] " patchwork-bot+bluetooth
  0 siblings, 2 replies; 3+ messages in thread
From: Andrew Sayers @ 2025-03-10 10:41 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: Andrew Sayers

The previous URL is out of date, and now just says
"This file has moved to process/submitting-patches.rst"
---
 HACKING | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/HACKING b/HACKING
index 29b136b34..5e07d91ea 100644
--- a/HACKING
+++ b/HACKING
@@ -116,7 +116,8 @@ The preferred way to send patches is by email, using git send-email:
   # git config sendemail.to linux-bluetooth@vger.kernel.org
 
 BlueZ rules for submitting patches follow most of the rules used by Linux kernel
-(https://www.kernel.org/doc/Documentation/SubmittingPatches) with some remarks:
+(https://www.kernel.org/doc/html/latest/process/submitting-patches.html)
+with some remarks:
 
 1) Do *not* add "Signed-off-by" lines in your commit messages. BlueZ does not
 use them, so including them is actually an error.
-- 
2.47.2


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-03-12 16:50 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-10 10:41 [PATCH BlueZ] Fix URL for submitting patches Andrew Sayers
2025-03-10 12:04 ` [BlueZ] " bluez.test.bot
2025-03-12 16:50 ` [PATCH BlueZ] " patchwork-bot+bluetooth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox