From: list at eworm.de (Christian Hesse)
Subject: [PATCH 1/1] ui-repolist: do not return unsigned (negative) value
Date: Fri, 22 Nov 2019 13:41:52 +0100 [thread overview]
Message-ID: <20191122134152.3b9597a7@leda> (raw)
In-Reply-To: <CAHmME9p4UAsCR8TOsY8sOy5gBqf-aB6m5pJdQ8kPO142yuMk7Q@mail.gmail.com>
"Jason A. Donenfeld" <Jason at zx2c4.com> on Fri, 2019/11/22 13:30:
> Thanks, stick it in ch/for-jason and I'll merge it for next release.
Done. (Same for changes to update to git 2.24.0.)
--
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/20191122/79bbd01f/attachment.asc>
prev parent reply other threads:[~2019-11-22 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 10:12 list
2019-11-22 12:30 ` Jason
2019-11-22 12:41 ` list [this message]
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=20191122134152.3b9597a7@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).