Re: [PATCH] doc: update list archive reference to use lore.kernel.org

From: Dragan Simic <dsimic@manjaro.org>
Date: Oct 19, 2023, 00:24 UTC
Message-ID: <199df43378febcc746c78029c5f90d04@manjaro.org>
In-Reply-To: <xmqq7cnz741s.fsf@gitster.g>

On 2023-10-07 00:57, Junio C Hamano wrote:

Show 9 quoted lines

> No disrespect to other mailing list archives, but the local part of
> their URLs will become pretty much meaningless once the archives go
> out of service, and we learned the lesson hard way when $gmane
> stopped serving.
> 
> Let's point into https://lore.kernel.org/ for an article that can be
> found there, because the local part of the URL has the Message-Id:
> that can be used to find the same message in other archives, even if
> lore goes down.

You asked for this patch to be reviewed, so I did it. It looks perfectly fine to me.

Show 21 quoted lines

> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> 
>  Documentation/CodingGuidelines | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/CodingGuidelines 
> b/Documentation/CodingGuidelines
> index 65af8d82ce..71afc5b259 100644
> --- a/Documentation/CodingGuidelines
> +++ b/Documentation/CodingGuidelines
> @@ -24,7 +24,7 @@ code.  For Git in general, a few rough rules are:
> 
>     "Once it _is_ in the tree, it's not really worth the patch noise to
>     go and fix it up."
> -   Cf. http://lkml.iu.edu/hypermail/linux/kernel/1001.3/01069.html
> +   Cf. 
> https://lore.kernel.org/all/20100126160632.3bdbe172.akpm@linux-foundation.org/
> 
>   - Log messages to explain your changes are as important as the
>     changes themselves.  Clearly written code and in-code comments