> As I wrote in a follow up email, it changes formatting b/c you didn't
> change field widths and IMO using %# with a field width is mostly
> trouble to begin with. It's not the first time someone tries to do
> this without actually understanding the consequences of the change.
> Please, can we as
On Fri, Mar 13, 2020 at 22:26:05 -0400, Christos Zoulas wrote:
> > On Mar 13, 2020, at 10:25 PM, Valery Ushakov wrote:
> >
> > As I wrote in a follow up email, it changes formatting b/c you didn't
> > change field widths and IMO using %# with a field width is mostly
> > trouble to begin with. I
> On Mar 13, 2020, at 10:25 PM, Valery Ushakov wrote:
>
> As I wrote in a follow up email, it changes formatting b/c you didn't
> change field widths and IMO using %# with a field width is mostly
> trouble to begin with. It's not the first time someone tries to do
> this without actually under
On Fri, Mar 13, 2020 at 22:15:31 -0400, Christos Zoulas wrote:
> > This was not a part of the PR and is completely cosmetic (surely it
> > supports plain %x if it does support %#x). Why was this necessary?
> > (I know I would be quite miffed if someone made a change like that to
> > my code).
>
> This was not a part of the PR and is completely cosmetic (surely it
> supports plain %x if it does support %#x). Why was this necessary?
> (I know I would be quite miffed if someone made a change like that to
> my code).
Yes, that %x formatting change was not part of the PR, but I only changed
On Fri, Mar 13, 2020 at 17:09:14 -0700, Paul Goyette wrote:
> On Sat, 14 Mar 2020, Valery Ushakov wrote:
>
> > On Fri, Mar 13, 2020 at 14:17:42 -0400, Christos Zoulas wrote:
> >
> > > Log Message:
> > > PR/55068: sc.dying: Fix printf formats:
> > [...]
> > > - 0x% -> %#
> >
> > This was not a p
On Sat, 14 Mar 2020, Valery Ushakov wrote:
On Fri, Mar 13, 2020 at 14:17:42 -0400, Christos Zoulas wrote:
Log Message:
PR/55068: sc.dying: Fix printf formats:
[...]
- 0x% -> %#
This was not a part of the PR and is completely cosmetic (surely it
supports plain %x if it does support %#x). W
On Fri, Mar 13, 2020 at 14:17:42 -0400, Christos Zoulas wrote:
> Log Message:
> PR/55068: sc.dying: Fix printf formats:
[...]
> - 0x% -> %#
This was not a part of the PR and is completely cosmetic (surely it
supports plain %x if it does support %#x). Why was this necessary?
(I know I would be qu
> On Mar 13, 2020, at 12:25 PM, Jason Thorpe wrote:
>
>
>> On Mar 13, 2020, at 9:11 AM, Christos Zoulas wrote:
>>
>> I think this is better done in the driver, as other ports
>> do the same check and it catches bugs.
>
> x86 *explcitly* checks for 0 to skip work. If you want to find bugs, c
> On Mar 13, 2020, at 9:11 AM, Christos Zoulas wrote:
>
> I think this is better done in the driver, as other ports
> do the same check and it catches bugs.
x86 *explcitly* checks for 0 to skip work. If you want to find bugs, change
the most-often-used implementation maybe?
-- thorpej
In article <20200313034939.553d5f...@cvs.netbsd.org>,
Jason R Thorpe wrote:
>-=-=-=-=-=-
>
>Module Name: src
>Committed By: thorpej
>Date: Fri Mar 13 03:49:39 UTC 2020
>
>Modified Files:
> src/sys/arch/mips/mips: bus_dma.c
>
>Log Message:
>Allow len == 0 in bus_dmamap_sync().
I
Thanks for explaining!
christos
signature.asc
Description: Message signed with OpenPGP
On Fri, Mar 13, 2020 at 04:09:25PM -, Christos Zoulas wrote:
> Sorry I don't understand this change? How is that different than using
>
> err(EXIT_FAILURE, "initscr");
For crunched install media the older variant seems to pull in lots of libc
(libhack has a simple perror but no err/errx
In article <20200312155012.1ce50f...@cvs.netbsd.org>,
Roy Marples wrote:
>-=-=-=-=-=-
>
>Module Name: src
>Committed By: roy
>Date: Thu Mar 12 15:50:12 UTC 2020
>
>Modified Files:
> src/lib/libcurses: initscr.c
>
>Log Message:
>curses: use perror rather than err in initscr
>
>Ind
14 matches
Mail list logo