Date:Wed, 1 May 2024 22:27:02 +0200
From:Roland Illig
Message-ID: <754bd755-be0a-4eff-aa7b-d53fce9b4...@gmx.de>
| > Log Message:
| > next should increement by 1 not 2.
|
| Are you sure?
I agree, that change should be reverted.
"next" is even documented to be
Am 01.05.2024 um 21:59 schrieb Christos Zoulas:
> Module Name: src
> Committed By: christos
> Date: Wed May 1 19:59:08 UTC 2024
>
> Modified Files:
> src/lib/libutil: parsedate.y
>
> Log Message:
> next should increement by 1 not 2.
Are you sure? I get these test results:
> t_pars
On Mon, Apr 08, 2024 at 23:31:16 +0200, Roland Illig wrote:
> Am 08.04.2024 um 21:18 schrieb Valery Ushakov:
> > "=\017FIFTEEN\0"
> >
> > with its result a few lines below that has:
> >
> > BURST=0xf=FIFTEEN
>
> Thank you for explaining this example. I had a gut feeling that there
> would be
Am 08.04.2024 um 21:18 schrieb Valery Ushakov:
> "=\017FIFTEEN\0"
>
> with its result a few lines below that has:
>
> BURST=0xf=FIFTEEN
Thank you for explaining this example. I had a gut feeling that there
would be some hidden correlation between some octal/hexadecimal
combinations, but I coul
On Mon, Apr 08, 2024 at 20:21:07 +0200, Roland Illig wrote:
> I didn't eradicate _all_ hexadecimal examples, I just made each example
> use only one number base, not mix them both. There are both octal and
> hexadecimal examples in the manual page.
That's not what "prefer octal in examples" conve
Am 08.04.2024 um 03:24 schrieb Valery Ushakov:
> On Sun, Apr 07, 2024 at 14:28:27 +, Roland Illig wrote:
>
>> Log Message:
>> snprintb.3: clean up formatting and wording, prefer octal in examples
>>
>> Using hexadecimal character escapes requires separate string literals if
>> the description s
On Sun, Apr 07, 2024 at 14:28:27 +, Roland Illig wrote:
> Log Message:
> snprintb.3: clean up formatting and wording, prefer octal in examples
>
> Using hexadecimal character escapes requires separate string literals if
> the description starts with one of the letters A-F; octal character
> e
On Sun, Jan 21, 2024 at 21:31:23 +, Roland Illig wrote:
> and also didn't make it clear that a few bits were omitted from
> having descriptions.
I dislike this part. It's internally inconsistent as it doesn't add
the placeholders for the low bits; and in many real-life scenarios
there will b
Date:Mon, 7 Dec 2015 15:55:49 -0500
From:"Christos Zoulas"
Message-ID: <20151207205549.4f6c...@cvs.netbsd.org>
| Modified Files:
| src/lib/libutil: parsedate.3 parsedate.y
|
The change below got missed from the parsedate.3 update.
I assume you decided to
On Wed, Aug 07, 2013 at 10:51:59PM +, Paul Goyette wrote:
> Module Name: src
> Committed By: pgoyette
> Date: Wed Aug 7 22:51:59 UTC 2013
>
> Modified Files:
> src/lib/libutil: snprintb.3
>
> Log Message:
> Add an example using snprintb_m()
>
> Replace \*[Gt] and \*[Lt] with
On Wed, Aug 07, 2013 at 16:17:01 -0700, Paul Goyette wrote:
> >Module Name:src
> >Committed By: pgoyette
> >Date: Wed Aug 7 22:51:59 UTC 2013
> >
> >Modified Files:
> >src/lib/libutil: snprintb.3
> >
> >Log Message:
> >Add an example using snprintb_m()
> >
> >Replace \*[Gt
Module Name:src
Committed By: pgoyette
Date: Wed Aug 7 22:51:59 UTC 2013
Modified Files:
src/lib/libutil: snprintb.3
Log Message:
Add an example using snprintb_m()
Replace \*[Gt] and \*[Lt] with the simple characters > and < (OK wiz)
XXX Note that the examples currentl
In article <20130621081825.11fd...@cvs.netbsd.org>,
Thomas Klausner wrote:
>-=-=-=-=-=-
>
>Module Name: src
>Committed By: wiz
>Date: Fri Jun 21 08:18:25 UTC 2013
>
>Modified Files:
> src/lib/libutil: login_cap.3
>
>Log Message:
>Punctuation nit.
>(Shouldn't the whole line be .Dl
On Mon, Dec 31, 2012 at 10:21:09AM +, David Laight wrote:
> > > Modified Files:
> > > src/lib/libutil: efun.c
> > >
> > > Log Message:
> > > If malloc, calloc, or realloc returns NULL when a size of 0 was
> > > requested, which is allowed by pertinent standards, honor it instead
> > >
On Mon, Dec 31, 2012 at 02:59:13AM +0100, Joerg Sonnenberger wrote:
> On Sun, Dec 30, 2012 at 05:36:00PM +, David A. Holland wrote:
> > Module Name:src
> > Committed By: dholland
> > Date: Sun Dec 30 17:36:00 UTC 2012
> >
> > Modified Files:
> > src/lib/libutil:
On Mon, 31 Dec 2012, Joerg Sonnenberger wrote:
Log Message:
If malloc, calloc, or realloc returns NULL when a size of 0 was
requested, which is allowed by pertinent standards, honor it instead
of bombing.
Do not do this for calloc(x, y) where x != 0 && y != 0 but x*y == 0;
in that case bomb.
T
On Mon, Dec 31, 2012 at 02:59:13AM +0100, Joerg Sonnenberger wrote:
> > Modified Files:
> >src/lib/libutil: efun.c
> >
> > Log Message:
> > If malloc, calloc, or realloc returns NULL when a size of 0 was
> > requested, which is allowed by pertinent standards, honor it instead
> > of bom
On Sun, Dec 30, 2012 at 05:36:00PM +, David A. Holland wrote:
> Module Name: src
> Committed By: dholland
> Date: Sun Dec 30 17:36:00 UTC 2012
>
> Modified Files:
> src/lib/libutil: efun.c
>
> Log Message:
> If malloc, calloc, or realloc returns NULL when a size of 0 was
> requ
On Sun, Jul 22, 2012 at 10:21:14PM -0400, Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Mon Jul 23 02:21:14 UTC 2012
>
> Modified Files:
> src/lib/libutil: openpty.3
>
> Log Message:
> Mention how big the name can be.
I don't think we should leak inter
In article <4ec5a97e.2070...@free.fr>,
Jean-Yves Migeon wrote:
>On 13.11.2011 23:03, Christos Zoulas wrote:
>> Module Name: src
>> Committed By:christos
>> Date:Sun Nov 13 22:03:34 UTC 2011
>>
>> Modified Files:
>> src/lib/libutil: Makefile
>> Added Files:
>> src
On 13.11.2011 23:03, Christos Zoulas wrote:
Module Name:src
Committed By: christos
Date: Sun Nov 13 22:03:34 UTC 2011
Modified Files:
src/lib/libutil: Makefile
Added Files:
src/lib/libutil: getfstypename.3
Log Message:
add manual page
Just wondering: is there a
> | On Thu, Oct 20, 2011 at 09:37:59PM -0400, Christos Zoulas wrote:
> | > Module Name: src
> | > Committed By: christos
> | > Date: Fri Oct 21 01:37:59 UTC 2011
> | >
> | > Modified Files:
> | > src/lib/libutil: Makefile
> | >
> | > Log Message:
> | > Don't use = to assin
On Nov 2, 7:11am, net...@lists.veego.de (Bernd Ernesti) wrote:
-- Subject: Re: CVS commit: src/lib/libutil
| Hi,
|
| On Thu, Oct 20, 2011 at 09:37:59PM -0400, Christos Zoulas wrote:
| > Module Name:src
| > Committed By: christos
| > Date: Fri Oct 21 01:37:59
Hi,
On Thu, Oct 20, 2011 at 09:37:59PM -0400, Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Fri Oct 21 01:37:59 UTC 2011
>
> Modified Files:
> src/lib/libutil: Makefile
>
> Log Message:
> Don't use = to assing SRCS, but += so that we can remove snprint
On Oct 21, 9:33am, y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) wrote:
-- Subject: Re: CVS commit: src/lib/libutil
| hi,
|
| > Module Name:src
| > Committed By: christos
| > Date: Fri Oct 21 02:05:36 UTC 2011
| >
| > Modified Files:
| > src/lib
hi,
> Module Name: src
> Committed By: christos
> Date: Fri Oct 21 02:05:36 UTC 2011
>
> Modified Files:
> src/lib/libutil: Makefile
>
> Log Message:
> Add proc_compare
you forgot to commit proc_compare.3?
YAMAMOTO Takashi
>
>
> To generate a diff of this commit:
> cvs rdiff
Modified Files:
src/lib/libutil: util.3
Log Message:
Upon lukem@'s request, put the list of functions back.
thank you.
On Wed, May 05, 2010 at 07:35:41AM +0300, Jukka Ruohonen wrote:
| On Wed, May 05, 2010 at 01:05:02PM +1000, Luke Mewburn wrote:
| > Please revert this; manual pages and application development
| > tools are often installed on systems where the full source is not.
|
| But you always have
On Wed, May 05, 2010 at 01:05:02PM +1000, Luke Mewburn wrote:
> Please revert this; manual pages and application development
> tools are often installed on systems where the full source is not.
But you always have the header file. Shouldn't that be enough?
> As I mentioned in my reply to the simi
On Tue, May 04, 2010 at 07:07:12AM +, Jukka Ruohonen wrote:
| Module Name:src
| Committed By: jruoho
| Date: Tue May 4 07:07:12 UTC 2010
|
| Modified Files:
| src/lib/libutil: util.3
|
| Log Message:
| Remove the list of functions in the libu
30 matches
Mail list logo
