linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org, gcc@gcc.gnu.org
Subject: Re: [PATCH 00/16] Fixes; Document remaining stdint.h types
Date: Thu, 1 Oct 2020 13:41:30 +0200	[thread overview]
Message-ID: <2dc7f5d7-c134-9209-67c2-7aeda0ad651b@gmail.com> (raw)
In-Reply-To: <754766a8-6749-1d95-f0ba-999f1a123405@gmail.com>

Hi Michael,

I did it this way because then you have a clearly ordered list
of the commits, and in which order they go,
so I thought it might be easier for you (creating less conflicts).

And also, I can hold any more recent patches, such as __int128,
for when you finish applying the previous set, so I fix the
conflicts before you ever see them.

Don't you think?

I don't mind fixing for example patch 5,
and then rebasing the rest (and also the patches I didn't send yet),
and resending them as an answer to v1 00/16.

But if you still prefer smaller sets, I'll send you smaller sets.

It's just that these patches are usually very dependent of the
previous ones, and therefore prone to conflicts if you
don't apply them in the same exact order.

Your thoughts?

Thanks,

Alex

On 2020-10-01 13:32, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
> 
> On 10/1/20 12:15 PM, Alejandro Colomar wrote:
>> Hi Michael,
>>
>> Here are a few fixes (including one removing .br),
>> and then the remaining stdint types.
> 
> These very long patch series are a bit overwhelming for me.
> I'd have preferred a few smaller patch series. For example,
> I think I would have preferred 3 series like this:
> 
> 1-4
> 5-12
> 13-16
> 
> One reason is that the multiple parallel reply threads that
> sometimes occur can sometimes be rather difficult to track.
> (Your patches have started some quite useful conversations!)
> 
> For example, I suspect Jonathan's comments may trigger changes
> for patches 5-12.
> 
> For now, I'm applying 1-4 and 13-16. It looks like some reworking is
> going to be needed for the others. When you do resubmit them, please
> start a new thread (rather than replying into this thread).
> 
> Thanks,
> 
> Michael
> 
>> Alejandro Colomar (16):
>>    malloc_get_state.3: ffix
>>    system_data_types.7: srcfix
>>    system_data_types.7: srcfix
>>    system_data_types.7: srcfix
>>    system_data_types.7: Add int_fastN_t family of types
>>    int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3,
>>      int_fastN_t.3: New links to system_data_types(7)
>>    system_data_types.7: Add uint_fastN_t family of types
>>    uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3,
>>      uint_fastN_t.3: New links to system_data_types(7)
>>    system_data_types.7: Add int_leastN_t family of types
>>    int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3,
>>      int_leastN_t.3: New links to system_data_types(7)
>>    system_data_types.7: Add uint_leastN_t family of types
>>    uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3,
>>      uint_leastN_t.3: New links to system_data_types(7)
>>    system_data_types.7: Add 'intptr_t'
>>    intptr_t.3: New link to system_data_types(7)
>>    system_data_types.7: Add 'uintptr_t'
>>    uintptr_t.3: New link to system_data_types(7)
>>
>>   man3/int_fast16_t.3      |   1 +
>>   man3/int_fast32_t.3      |   1 +
>>   man3/int_fast64_t.3      |   1 +
>>   man3/int_fast8_t.3       |   1 +
>>   man3/int_fastN_t.3       |   1 +
>>   man3/int_least16_t.3     |   1 +
>>   man3/int_least32_t.3     |   1 +
>>   man3/int_least64_t.3     |   1 +
>>   man3/int_least8_t.3      |   1 +
>>   man3/int_leastN_t.3      |   1 +
>>   man3/intptr_t.3          |   1 +
>>   man3/malloc_get_state.3  |   2 +-
>>   man3/uint_fast16_t.3     |   1 +
>>   man3/uint_fast32_t.3     |   1 +
>>   man3/uint_fast64_t.3     |   1 +
>>   man3/uint_fast8_t.3      |   1 +
>>   man3/uint_fastN_t.3      |   1 +
>>   man3/uint_least16_t.3    |   1 +
>>   man3/uint_least32_t.3    |   1 +
>>   man3/uint_least64_t.3    |   1 +
>>   man3/uint_least8_t.3     |   1 +
>>   man3/uint_leastN_t.3     |   1 +
>>   man3/uintptr_t.3         |   1 +
>>   man7/system_data_types.7 | 590 ++++++++++++++++++++++++++++++++++-----
>>   24 files changed, 540 insertions(+), 74 deletions(-)
>>   create mode 100644 man3/int_fast16_t.3
>>   create mode 100644 man3/int_fast32_t.3
>>   create mode 100644 man3/int_fast64_t.3
>>   create mode 100644 man3/int_fast8_t.3
>>   create mode 100644 man3/int_fastN_t.3
>>   create mode 100644 man3/int_least16_t.3
>>   create mode 100644 man3/int_least32_t.3
>>   create mode 100644 man3/int_least64_t.3
>>   create mode 100644 man3/int_least8_t.3
>>   create mode 100644 man3/int_leastN_t.3
>>   create mode 100644 man3/intptr_t.3
>>   create mode 100644 man3/uint_fast16_t.3
>>   create mode 100644 man3/uint_fast32_t.3
>>   create mode 100644 man3/uint_fast64_t.3
>>   create mode 100644 man3/uint_fast8_t.3
>>   create mode 100644 man3/uint_fastN_t.3
>>   create mode 100644 man3/uint_least16_t.3
>>   create mode 100644 man3/uint_least32_t.3
>>   create mode 100644 man3/uint_least64_t.3
>>   create mode 100644 man3/uint_least8_t.3
>>   create mode 100644 man3/uint_leastN_t.3
>>   create mode 100644 man3/uintptr_t.3
>>
> H
> 

  reply	other threads:[~2020-10-01 11:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 10:15 [PATCH 00/16] Fixes; Document remaining stdint.h types Alejandro Colomar
2020-10-01 10:15 ` [PATCH 01/16] malloc_get_state.3: ffix Alejandro Colomar
2020-10-01 11:32   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 02/16] system_data_types.7: srcfix Alejandro Colomar
2020-10-01 11:33   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 03/16] " Alejandro Colomar
2020-10-01 11:33   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 04/16] " Alejandro Colomar
2020-10-01 11:34   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 05/16] system_data_types.7: Add int_fastN_t family of types Alejandro Colomar
2020-10-01 11:07   ` Jonathan Wakely
2020-10-01 11:15     ` Alejandro Colomar
2020-10-01 11:27       ` Jonathan Wakely
2020-10-01 14:16         ` Alejandro Colomar
2020-10-01 15:13     ` Alejandro Colomar
2020-10-01 10:15 ` [PATCH 06/16] int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3, int_fastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 10:15 ` [PATCH 07/16] system_data_types.7: Add uint_fastN_t family of types Alejandro Colomar
2020-10-01 10:15 ` [PATCH 08/16] uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3, uint_fastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 10:15 ` [PATCH 09/16] system_data_types.7: Add int_leastN_t family of types Alejandro Colomar
2020-10-01 10:15 ` [PATCH 10/16] int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3, int_leastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 10:15 ` [PATCH 11/16] system_data_types.7: Add uint_leastN_t family of types Alejandro Colomar
2020-10-01 10:15 ` [PATCH 12/16] uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3, uint_leastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 10:15 ` [PATCH 13/16] system_data_types.7: Add 'intptr_t' Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 14/16] intptr_t.3: New link to system_data_types(7) Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 15/16] system_data_types.7: Add 'uintptr_t' Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 10:16 ` [PATCH 16/16] uintptr_t.3: New link to system_data_types(7) Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 11:32 ` [PATCH 00/16] Fixes; Document remaining stdint.h types Michael Kerrisk (man-pages)
2020-10-01 11:41   ` Alejandro Colomar [this message]
2020-10-01 11:50     ` Michael Kerrisk (man-pages)
2020-10-01 11:51       ` 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=2dc7f5d7-c134-9209-67c2-7aeda0ad651b@gmail.com \
    --to=colomar.6.4.3@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).