From 84ac264aeadf6adb37e20033d6756870a169bb57 Mon Sep 17 00:00:00 2001 From: Alejandro Colomar Date: Thu, 19 Dec 2024 11:33:43 +0100 Subject: [PATCH] CONTRIBUTING.d/patches/subject: Use the full path always This is easier to do, since auto-completion will do it. Also, it's more consistent. I started using full paths a few commits ago. Signed-off-by: Alejandro Colomar --- CONTRIBUTING.d/patches/subject | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.d/patches/subject b/CONTRIBUTING.d/patches/subject index 208bb9ef8..0493d7436 100644 --- a/CONTRIBUTING.d/patches/subject +++ b/CONTRIBUTING.d/patches/subject @@ -6,14 +6,11 @@ Description the commit message). File names - Mention the name(s) of the file(s) being patched. + Mention the name(s) of the file(s) being patched. Write the + full path. When several files in a directory are modified, + write the name of the directory, with a trailing '/'. Example: - When the files are manual pages, you should write only the - basename(1). Otherwise, write the full path. When several - files in a directory are modified, write the name of the - directory, with a trailing '/'. Example: - - [PATCH v1] shmop.2: Add "(void *)" cast to RETURN VALUE + [PATCH v1] man/man2/shmop.2: Add "(void *)" cast to RETURN VALUE English sentence The subject line after the file-name prefix should be a correct -- 2.47.2