From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com, nab <nabijaczleweli@nabijaczleweli.xyz>,
"G . Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [RFC 0/3] Prepare the Makefile and scripts/ for releasing
Date: Sat, 16 Apr 2022 01:33:09 +0200 [thread overview]
Message-ID: <abd2a499-cd4e-4ca4-3217-fd4012ed9b29@gmail.com> (raw)
In-Reply-To: <20220415233048.70477-1-alx.manpages@gmail.com>
On 4/16/22 01:30, Alejandro Colomar wrote:
> ./scripts/append_COLOPHON.sh
> make dist-gz
I meant s/dist-gz/dist/
prev parent reply other threads:[~2022-04-15 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 23:30 [RFC 0/3] Prepare the Makefile and scripts/ for releasing Alejandro Colomar
2022-04-15 23:30 ` [PATCH 1/3] scripts/remove_COLOPHON.sh: Allow passing directories to the script Alejandro Colomar
2022-04-15 23:30 ` [PATCH 2/3] scripts/append_COLOPHON.sh: Add script to append the COLOPHON section Alejandro Colomar
2022-04-15 23:30 ` [PATCH 3/3] Makefile: dist: Add target to create distribution archives Alejandro Colomar
2022-04-16 13:02 ` [RFC v3 " Alejandro Colomar
2022-04-15 23:33 ` 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=abd2a499-cd4e-4ca4-3217-fd4012ed9b29@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox