From: Alejandro Colomar <alx.manpages@gmail.com>
To: Sam James <sam@gentoo.org>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: man-pages RELEASE file
Date: Thu, 20 Oct 2022 11:27:12 +0200 [thread overview]
Message-ID: <8239573f-4d28-7ce0-644d-792d0bbc02c7@gmail.com> (raw)
In-Reply-To: <7269B9BC-ABFA-4738-B308-C65CD3E1B211@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
Hi Sam,
On 10/20/22 05:41, Sam James wrote:
>> On 19 Oct 2022, at 13:51, Alejandro Colomar <alx.manpages@gmail.com> wrote:
>> I just added a file RELEASE, officially documenting how a release is made, in case I disappear at some point, someone can pick it and know what to do.
>>
>> The most interesting part to you from that file, is that it also covers the case of someone wanting to package a random commit. It's as trivial as running 'make dist', but it's better if it's documented. ;)
>>
>
> Fantastic, thanks for thinking of (an unthinkable/the) future! >
> I'll try find an excuse to try the instructions for real, too.
Just take into account that the RELEASE file doesn't match exactly how
6.00 and 6.01 have been done, but rather how I'd do 6.02 after learning
from these. When you try the instructions, give preference to what you
read in the RELEASE document if it differs from what I've done in the past.
If you find any issues following it, please report them! :-)
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-20 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 12:51 man-pages RELEASE file Alejandro Colomar
2022-10-20 3:41 ` Sam James
2022-10-20 9:27 ` Alejandro Colomar [this message]
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=8239573f-4d28-7ce0-644d-792d0bbc02c7@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=sam@gentoo.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.