Hey guys.
I was warned by the compiler about a misleading indentation and I
think its right.
http://git.suckless.org/sbase/tree/paste.c#n70
It's missing brackets or last++ must lose 1 level of indentation.
I think the first. Right?
Best wishes.
Hey guys.
The missing brackets on paste.c that I talked about on the last
message revealed something else to me.
It was introduced in commit cdbc0d50356a0f7e0dd5755e3c46593a947cf029
by FRIGN, 2015-01-29.
Then it was marked as audited and correct in commit
1bc002b44acdbfec8d374bfd0e5a858a142c0378
On Thu, 1 Sep 2016 11:46:36 -0300
Marc Collin wrote:
Hey Marc,
> The missing brackets on paste.c that I talked about on the last
> message revealed something else to me.
>
> It was introduced in commit cdbc0d50356a0f7e0dd5755e3c46593a947cf029
> by FRIGN, 2015-01-29.
>
> Then it was marked as a
On 2016-09-01 17:46, Marc Collin wrote:
Hey guys.
The missing brackets on paste.c that I talked about on the last
message revealed something else to me.
It was introduced in commit cdbc0d50356a0f7e0dd5755e3c46593a947cf029
by FRIGN, 2015-01-29.
Then it was marked as audited and correct in commi
Yeah, I'm not complaining about the audits, I remember they found many bugs!
It was just a random thing that came to me - normally a person that
makes a mistake will overlook the mistake. But someone from the
outside should spot it more easily.
I don't even know if this is true, but I think it is b
On 2016-09-01 18:34, Marc Collin wrote:
Since we're talking about sbase already in kind of meta way, I'll post
a question here instead of a new email.
sbase is basically ready, right? The few missing tools are not yet
applied, but were sent to the ML by maandree some months ago (patch,
diff and o
>http://git.suckless.org/sbase/tree/TODO
>at
https://github.com/maandree/sat
>awk
http://lists.suckless.org/dev/1602/28382.html
>bc
https://github.com/suiginsoft/bc
>diff
http://lists.suckless.org/hackers/1603/10326.html
>patch
http://lists.suckless.org/hackers/1603/10410.html
>stty
http://li
On Thu, 1 Sep 2016 12:34:12 -0300
Marc Collin wrote:
Hey Marc,
> Yeah, I'm not complaining about the audits, I remember they found
> many bugs! It was just a random thing that came to me - normally a
> person that makes a mistake will overlook the mistake. But someone
> from the outside should s
Hi!
Added IPv6 to lnanohttp and lnanosmtp:
https://github.com/sylware/lnanohttp
https://github.com/sylware/lnanosmtp
https://repo.or.cz/lnanosmtp.git
https://repo.or.cz/lnanohttp.git
cheers,
--
Sylvain
On Thu, 1 Sep 2016 21:53:21 +0200
Sylvain BERTRAND wrote:
Hey Sylvain,
> Added IPv6 to lnanohttp and lnanosmtp:
how do you expect anyone to use your software when you ship your own
"libc" called "ulinux"? Why would I use this piece of software when
it's unportable and only available for x86 and
On Thu, Sep 01, 2016 at 10:14:18PM +0200, FRIGN wrote:
> On Thu, 1 Sep 2016 21:53:21 +0200
> Sylvain BERTRAND wrote:
>
> Hey Sylvain,
>
> > Added IPv6 to lnanohttp and lnanosmtp:
>
> how do you expect anyone to use your software when you ship your own
> "libc" called "ulinux"? Why would I use t
On Thu, Sep 01, 2016 at 10:14:18PM +0200, FRIGN wrote:
> On Thu, 1 Sep 2016 21:53:21 +0200
> Sylvain BERTRAND wrote:
>
> Hey Sylvain,
>
> > Added IPv6 to lnanohttp and lnanosmtp:
>
> how do you expect anyone to use your software when you ship your own
> "libc" called "ulinux"? Why would I use t
On Fri, 2 Sep 2016 06:36:54 +0200
Markus Wichmann wrote:
Hey Markus,
> Oh come on, it's all of five minutes' work to compile this software
> against any libc you want. And all of an hour's work to replace all
> the printf() calls with something reasonable and reduce binary size
> way further tha
13 matches
Mail list logo
