From: list at eworm.de (Christian Hesse)
Subject: [PATCH] cgit.css: add dynamic age update
Date: Mon, 25 Jun 2018 00:58:06 +0200 [thread overview]
Message-ID: <20180625005806.4585133e@leda> (raw)
In-Reply-To: <20180624115253.GM6584@john.keeping.me.uk>
John Keeping <john at keeping.me.uk> on Sun, 2018/06/24 12:52:
> I'd really like to here other people's opinions on this.
I like this change, but we should keep js optional and not break existing
functionality without it. (I did not look at the code, but discussion sounds
like it is good as-is.)
--
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/20180625/11e0aeae/attachment.asc>
next prev parent reply other threads:[~2018-06-24 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 7:59 andy
2018-06-24 11:52 ` john
2018-06-24 12:11 ` andy
2018-06-24 22:58 ` list [this message]
2018-06-25 0:15 ` andy
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=20180625005806.4585133e@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).