From: list at eworm.de (Christian Hesse)
Subject: [PATCH 1/1] filters: in markdown get images from their plain url
Date: Thu, 17 Apr 2014 14:14:39 +0200 [thread overview]
Message-ID: <20140417141439.3b4043c4@leda.localdomain> (raw)
In-Reply-To: <CAHmME9ru4Dw_d6LnQNZ03JuK1tzVw8SFA6PO3EAiSyhW_PjLyw@mail.gmail.com>
"Jason A. Donenfeld" <Jason at zx2c4.com> on Thu, 2014/04/17 13:44:
> Hmm still not perfect though. Let's say I want a relative URL that is
> out of the cgit root but still on the same domain...
Probably it's better to do it right... The best solution
would be to have cgit itself handle it. Looking at the mime type may
be an option, just returning binary data in case of an image.
Sadly cgit has already printed some html stuff when about_fn() is called...
Looks like this would require some bigger changes.
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140417/52f71243/attachment-0001.asc>
next prev parent reply other threads:[~2014-04-17 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 10:13 Images on about page list
2014-04-17 10:18 ` list
2014-04-17 10:19 ` [PATCH 1/1] filters: in markdown get images from their plain url mail
2014-04-17 10:57 ` Jason
2014-04-17 11:02 ` mail
2014-04-17 11:42 ` mail
2014-04-17 11:44 ` Jason
2014-04-17 12:14 ` list [this message]
2014-04-17 13:19 ` [PATCH 1/1] about: return images in plain mode mail
2014-04-17 13:21 ` list
2014-04-30 8:37 ` mail
2014-06-29 20:14 ` list
2014-06-29 21:07 ` Jason
2014-06-30 6:31 ` list
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=20140417141439.3b4043c4@leda.localdomain \
--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).