All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillem Jover <guillem@hadrons.org>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Oskari Pirhonen <xxc3ncoredxx@gmail.com>,
	linux-man@vger.kernel.org, Brian Inglis <Brian.Inglis@shaw.ca>,
	Matt Jolly <Matt.Jolly@footclan.ninja>
Subject: Re: Revert "Many Pages: Remove references to C89"
Date: Wed, 15 Mar 2023 05:36:00 +0100	[thread overview]
Message-ID: <ZBFLMHHTxwhzXYWf@thunder.hadrons.org> (raw)
In-Reply-To: <591290fb-e78d-ad3a-8b25-4a860d26f775@gmail.com>

Hi!

I had in mind starting a similar thread like this some days ago, but
did not find the time, so thanks for doing that!

On Mon, 2023-03-13 at 13:00:52 +0100, Alejandro Colomar wrote:
> On 3/13/23 02:42, Oskari Pirhonen wrote:
> > "Usefulness" seems to be a hard sell for you, but perhaps you would
> > reconsider it based on the historical relevance of C89? It was, after
> > all, the first proper standard of the C language. If you don't want to
> > promote C89 by having it mentioned alongside the others, perhaps you'd
> > be open to the idea of adding a historical note?

> I've been considering something like that for a long time.  The
> STANDARDS section (previously known as CONFORMING TO), is a mix of a
> proper standards section, and what a HISTORY section should contain.
> 
> It would be interesting to do a split, and inaugurate a HISTORY section.
> For that section, I would keep any references to C89, since as you say
> it's historically very relevant.  Thus, I will revert the patch, and later apply some patches that move the info without discarding it.

As long as the information is preserved, because as has been mentioned
in the thread it is helpful when dealing with codebases that restrict
to C89 for whatever reason, this seems good. :) And also to canvas for
how long an interface has been around.

> > Saying that C89 is
> > obsolete in the note would be acceptable IMO, but not having any mention
> > of C89 at all makes the manpages feel incomplete. Others have shared
> > this sentiment when chatting with them online.

For me what seemed rather confusing was that mentions of C89 were
removed but there are references to stuff like «4.xBSD», so I guess
that's why it felt incomplete to me too. (Not suggesting to remove
those either! But I guess this might have planted the idea now. :)

In any case, thanks for the revert!

Regards,
Guillem

  parent reply	other threads:[~2023-03-15  5:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  1:51 Revert "Many Pages: Remove references to C89" Matt Jolly
2023-03-10  1:51 ` [PATCH] Revert "Many pages: " Matt Jolly
2023-03-10  2:22 ` Revert "Many Pages: " Alejandro Colomar
2023-03-10  5:00   ` Oskari Pirhonen
2023-03-10 13:29     ` Alejandro Colomar
2023-03-10 13:32       ` Alejandro Colomar
2023-03-13  1:42       ` Oskari Pirhonen
2023-03-13 12:00         ` Alejandro Colomar
2023-03-14  5:39           ` Oskari Pirhonen
2023-03-15 12:30             ` Alejandro Colomar
2023-03-15 12:53               ` Alejandro Colomar
2023-03-15 12:54                 ` Alejandro Colomar
2023-03-15 14:22                 ` Alejandro Colomar
2023-03-15 16:51               ` Brian Inglis
2023-03-15 17:01                 ` Alejandro Colomar
2023-03-15 18:10                   ` Tom Schwindl
2023-03-16  1:43                     ` Alejandro Colomar
2023-03-18  4:58                       ` Oskari Pirhonen
2023-03-22  1:20                         ` Alejandro Colomar
2023-03-15  4:36           ` Guillem Jover [this message]
2023-03-10  6:40   ` Brian Inglis
2023-03-10 12:49     ` Alejandro Colomar
2023-03-23  5:32   ` Sam James
2023-03-23 13:13     ` 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=ZBFLMHHTxwhzXYWf@thunder.hadrons.org \
    --to=guillem@hadrons.org \
    --cc=Brian.Inglis@shaw.ca \
    --cc=Matt.Jolly@footclan.ninja \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=xxc3ncoredxx@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.