From: peter at colberg.org (Peter Colberg)
Subject: [PATCH 0/3] Fix segfault found by AFL
Date: Sun, 19 Feb 2017 20:48:51 -0500 [thread overview]
Message-ID: <20170220014851.djhpw7ohyeb3y5qn@ceyx> (raw)
In-Reply-To: <CAHmME9rYXHZBPp_sXxhyWr8eL68yynzsci2U1biocWW0htYZ6g@mail.gmail.com>
Hi Jason,
On Sun, Feb 19, 2017 at 08:04:49PM +0100, Jason A. Donenfeld wrote:
> Excellent. Running AFL on cgit is a great idea. I'll merge and review when
> I'm back at my desk on Tuesday.
Could you release a bugfix v1.1.1 afterwards? Debian is preparing for
the release of stretch and it would be perfect if I could upload a new
upstream version instead of cherry-picking the fixes.
Regards,
Peter
prev parent reply other threads:[~2017-02-20 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 12:44 john
2017-02-19 12:44 ` [PATCH 1/3] ui-shared: don't print path crumbs without a repo john
2017-02-19 12:45 ` [PATCH 2/3] parsing: clear query path before starting john
2017-02-19 12:45 ` [PATCH 3/3] cgit: don't set vpath unless repo is set john
[not found] ` <CAHmME9r8zY9qOqbg7fwuB1gW76nXVcsqJ-LT2-6sjD3SuoJ-HQ@mail.gmail.com>
2017-02-19 19:04 ` [PATCH 0/3] Fix segfault found by AFL Jason
2017-02-20 1:48 ` peter [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=20170220014851.djhpw7ohyeb3y5qn@ceyx \
--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).