All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 07/13] libc.7: ffix
Date: Fri, 6 Jan 2023 13:06:55 +0100	[thread overview]
Message-ID: <96a187c4-4d5c-3719-2c51-6ac43bb33ba1@gmail.com> (raw)
In-Reply-To: <20230106071642.ukwraci3kp5sa74r@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 1556 bytes --]

Hi Branden,

On 1/6/23 08:16, G. Branden Robinson wrote:
>> Where did this idea of separating it in synopses come from? Maybe
>> logic thinking, such as placing the period outside of quotes...
> 
> My _guess_ as to the _reason_ is as I said earlier--to reinforce the
> idea that the optional arguments are whitespace-separated.  As for where
> it came from, the strongest historical claim I can readily make is that
> it appears in the earliest Unix man pages for which we have hard copy.
> 
> So that would be the ar(I) page in the (First Edition) Unix Programmer's
> Manual, dated 3 November 1971.  (Image attached.)

Interesting.

> 
>> So, I guess I'll pick that patch.  I'll tell you if I do.
> 
> When you've reported one as applied, should I drop it from my further
> revisions of the patch group?

Yes.  When I report that I applied a patch, it means that I applied it to my 
main branch, and that it will imminently be pushed to the master branch at 
kernel.org.  Some times it is immediate, and some times I delay it for a few 
hours or days, if I have patches that concern me in the branch.

I pushed my main branch to my own remote so that you can rebase on top of that 
(if I later remove the bzero patch from there, it shouldn't create any conflicts 
to your patches).

<http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/log/>
<git://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git>

> 
> Regards,
> Branden

Cheers,

Alex

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

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

  parent reply	other threads:[~2023-01-06 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 22:53 [PATCH v3 07/13] libc.7: ffix G. Branden Robinson
2023-01-05 23:53 ` Alejandro Colomar
2023-01-06  0:17   ` G. Branden Robinson
2023-01-06  0:39     ` Alejandro Colomar
2023-01-06  7:25       ` G. Branden Robinson
     [not found]       ` <20230106071642.ukwraci3kp5sa74r@illithid>
2023-01-06 12:06         ` Alejandro Colomar [this message]
2023-01-06  7:24     ` How Groupe Bull screwed French with ISO 8859-1 (was: [PATCH v3 07/13] libc.7: ffix) G. Branden Robinson
2023-01-06 23:40 ` [PATCH v3 07/13] libc.7: ffix Alejandro Colomar
2023-01-08 22:59   ` G. Branden Robinson

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=96a187c4-4d5c-3719-2c51-6ac43bb33ba1@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.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.