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
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 ge
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,
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 wo
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 fa