From: list at eworm.de (Christian Hesse)
Subject: [PATCH 1/2] cgit: introduce parse_{bool, int}() for for cgitrc parsing
Date: Mon, 7 Jan 2019 21:54:50 +0100 [thread overview]
Message-ID: <20190107215450.497c82e2@leda> (raw)
In-Reply-To: <20190107153535.21620-1-list@eworm.de>
Christian Hesse <list at eworm.de> on Mon, 2019/01/07 16:35:
> From: Christian Hesse <mail at eworm.de>
>
> We used to have atoi() only for parsing of numeric and boolean (numeric
> evaluating true or false) values. Let's introduce parse_{bool,int}()
> for minimal sanitization.
Please give this a good review to make sure I did not mess up. :-p
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20190107/43fb1cb0/attachment-0001.asc>
next prev parent reply other threads:[~2019-01-07 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 14:38 [PATCH 1/1] cgitrc: handle value "0" for max-repo-count list
2018-07-16 14:41 ` list
2018-09-11 6:56 ` list
2018-10-18 22:52 ` Jason
2018-11-23 16:08 ` list
2018-12-07 4:10 ` Jason
2019-01-07 15:34 ` list
2019-01-07 15:35 ` [PATCH 1/2] cgit: introduce parse_{bool, int}() for for cgitrc parsing list
2019-01-07 15:35 ` [PATCH 2/2] cgit: sanitize max-repo-count list
2019-01-07 20:54 ` list [this message]
2019-01-08 14:05 ` [PATCH 1/2] cgit: introduce parse_{bool, int}() for for cgitrc parsing whydoubt
2019-01-10 19:23 ` [PATCH 1/1] cgitrc: handle value "0" for max-repo-count tlatorre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190107215450.497c82e2@leda \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).