All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>, Stefan Puiu <stefan.puiu@gmail.com>,
	Jakub Wilk <jwilk@jwilk.net>, lnx-man <linux-man@vger.kernel.org>
Subject: Ping: Re: Move man* to man/ (was: Revert 70ac1c478 ("src.mk, All pages: Move man* to man/"))
Date: Fri, 26 Apr 2024 14:43:02 +0200	[thread overview]
Message-ID: <ZiuhVmLAnm2r5xaQ@debian> (raw)
In-Reply-To: <ZgIk4mN4bXfsiiYy@debian>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Hi!

On Tue, Mar 26, 2024 at 02:28:59AM +0100, Alejandro Colomar wrote:
> I'm thinking of adding some features to the build system that would need
> having a clean man/ directory.  The main one is building several books
> for other projects, one per language, where languages correspond to
> every directory within man/ that doesn't match man*.  Currently, I'm
> workarounding this by running the build system several times, for each
> language dir, but it could be much simpler, I think.
> 
> For not having a regression in the number of characters one needs to
> type to edit the manual pages, I thought of adding symlinks in the root
> of the repository, so it would look like this:

[...]

> What do you think about it?

Ping.

To be explicit: I want to

$ mkdir man/
$ mv man* man/
$ ln -st . man/man*

Should I assume that no-one has reasons against this?  I'll still take
some time before doing the change, to allow replies to this thread.  But
please manifest youselves, even if just for saying you don't have an
opinion.  Thanks!

Have a lovely day!
Alex

> 
> Cheers,
> Alex

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-26 12:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  9:41 Revert 70ac1c478 ("src.mk, All pages: Move man* to man/") Petr Vorel
2022-09-06 11:19 ` Alejandro Colomar
2022-09-06 11:57   ` Alejandro Colomar
2022-09-06 11:58     ` Alejandro Colomar
2022-09-06 16:09   ` Petr Vorel
2022-09-07 20:53 ` Jakub Wilk
2022-09-07 22:11   ` Alejandro Colomar
2022-09-08 12:42     ` Stefan Puiu
2022-09-09  8:46       ` Petr Vorel
2022-09-15 13:40         ` Alex Colomar
2022-09-15 13:48           ` Petr Vorel
2023-08-02 21:38           ` Alejandro Colomar
2023-08-02 21:45             ` Alejandro Colomar
2024-03-26  1:28         ` Move man* to man/ (was: Revert 70ac1c478 ("src.mk, All pages: Move man* to man/")) Alejandro Colomar
2024-04-26 12:43           ` Alejandro Colomar [this message]
2024-04-26 18:03             ` Ping: " Petr Vorel
2024-04-26 20:19               ` Alejandro Colomar

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=ZiuhVmLAnm2r5xaQ@debian \
    --to=alx@kernel.org \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=pvorel@suse.cz \
    --cc=stefan.puiu@gmail.com \
    /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.