Message ID | 20201001101559.77163-1-colomar.6.4.3@gmail.com |
---|---|
Headers |
Return-Path: <libc-alpha-bounces@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 9F3AD3953422; Thu, 1 Oct 2020 10:16:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9F3AD3953422 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1601547392; bh=uoB2FuCKSAsI6kIXOPfmwCNt6BZv8rUUkPrUn9rLEWU=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:Cc:From; b=GNSS9fYi0Ao05HTcNYVQT1Zz1E8q8FWB+7A727eH0IKt0AxYZvMLIGkDH+T9gofoM yeKxaZs7NSHwbLn0YRY8Mqwq0Z6tgASjQGcRNGFQCmtJkALdJkr3iI1GtyfFcZPIY8 EU4OqiXn/QvuKNUwICdI6tXjABTTqDvZUhCV8TD8= X-Original-To: libc-alpha@sourceware.org Delivered-To: libc-alpha@sourceware.org Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) by sourceware.org (Postfix) with ESMTPS id CCEE53857024 for <libc-alpha@sourceware.org>; Thu, 1 Oct 2020 10:16:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org CCEE53857024 Received: by mail-wm1-x32a.google.com with SMTP id q9so2321966wmj.2 for <libc-alpha@sourceware.org>; Thu, 01 Oct 2020 03:16:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=uoB2FuCKSAsI6kIXOPfmwCNt6BZv8rUUkPrUn9rLEWU=; b=IdBaOAJ591Drgg0Kzk4eFn9Kp1SMBIDr7WpczN2e0eBFm3DyVbNtEZnydTfHrGK+zL f1Zh1JKmhSMLqtTngH6l/obqnGaLJ2cFAczd+hlIPmQkosLGgF1Eu+JkGI9Zqdg4+UQf ahLDroWeUGjuFX0zjUEIiBKewABN2W13jURCEFbk3NgRARLBj52l4WjmoqjW5gUtTY8m ijNHPlpoHQpRaLkCp0T/0XtT/CkkAtZj8w8iipoz5aSL01ltf6UjawqOvBeGotPasGCq dXpGjq2PmXM8u2ZSnk1GkyOQKgAC5q4uyydjmlk2B/FSw736a78qX0EBnjqGT0/aGazu Boxg== X-Gm-Message-State: AOAM533Oas/0aRahaSf7dFAMMGiRzJUAvB3dao5kK/kW20wuFBrTsI/e DajVvz1rOjjBkplxbfPYxoxvsJSMlYbEJQ== X-Google-Smtp-Source: ABdhPJwrLlkMbUrUr7pWU9fr54ldFC4OrnbmY9WLOQUz0WXXNYYLz7+lWyepSv70iU2xnjdZBHMyRQ== X-Received: by 2002:a05:600c:24d:: with SMTP id 13mr7822149wmj.86.1601547388840; Thu, 01 Oct 2020 03:16:28 -0700 (PDT) Received: from localhost.localdomain ([170.253.60.68]) by smtp.googlemail.com with ESMTPSA id i15sm8671922wrb.91.2020.10.01.03.16.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Oct 2020 03:16:28 -0700 (PDT) To: mtk.manpages@gmail.com Subject: [PATCH 00/16] Fixes; Document remaining stdint.h types Date: Thu, 1 Oct 2020 12:15:44 +0200 Message-Id: <20201001101559.77163-1-colomar.6.4.3@gmail.com> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list <libc-alpha.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/libc-alpha>, <mailto:libc-alpha-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/libc-alpha/> List-Post: <mailto:libc-alpha@sourceware.org> List-Help: <mailto:libc-alpha-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/libc-alpha>, <mailto:libc-alpha-request@sourceware.org?subject=subscribe> From: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org> Reply-To: Alejandro Colomar <colomar.6.4.3@gmail.com> Cc: colomar.6.4.3@gmail.com, linux-man@vger.kernel.org, libc-alpha@sourceware.org, gcc@gcc.gnu.org Errors-To: libc-alpha-bounces@sourceware.org Sender: "Libc-alpha" <libc-alpha-bounces@sourceware.org> |
Series |
Fixes; Document remaining stdint.h types
|
|
Message
Alejandro Colomar
Oct. 1, 2020, 10:15 a.m. UTC
Hi Michael, Here are a few fixes (including one removing .br), and then the remaining stdint types. Cheers, Alex 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
Comments
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
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 >
Hi Alex, On 10/1/20 1:41 PM, Alejandro Colomar wrote: > 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). Yes, I understand the rationale. But when I get a series of loosely related patches in a series of 20, and multiple conversations start about independent topics, I'm finding it quite some effort to keep track. > 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. I do prefer smaller sets. And yes, occasionally things may go wrong in terms of patch conflicts, but I think that may be a smaller than the problem I note above. > 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? As you can see, there's no perfect solution here. In such situations what I try to do (where possible) is order the patches from least contentious to most contentious. That way, the patches that are almost certainly going to be applied are loaded at the front and the chance of having to rebasing later patches in a series is lower. Thanks, Michael > 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 >>
Okay then :) Thanks, Alex On 2020-10-01 13:50, Michael Kerrisk (man-pages) wrote: > Hi Alex, > > On 10/1/20 1:41 PM, Alejandro Colomar wrote: >> 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). > > Yes, I understand the rationale. But when I get a series of > loosely related patches in a series of 20, and multiple > conversations start about independent topics, I'm finding > it quite some effort to keep track. > >> 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. > > I do prefer smaller sets. And yes, occasionally things may > go wrong in terms of patch conflicts, but I think that may be > a smaller than the problem I note above. > >> 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? > > As you can see, there's no perfect solution here. In such > situations what I try to do (where possible) is order the > patches from least contentious to most contentious. > That way, the patches that are almost certainly going to > be applied are loaded at the front and the chance of having > to rebasing later patches in a series is lower. > > Thanks, > > Michael > > > >> 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