From: lfleischer at lfos.de (Lukas Fleischer)
Subject: [PATCH] ui-patch: fix segfault when a path prefix is passed
Date: Mon, 23 Jan 2017 09:38:08 +0100 [thread overview]
Message-ID: <148516068856.17037.16353040829889778712@typhoon> (raw)
In-Reply-To: <CAHmME9otS_R=Of=K1K2yomF2+ojoE7cvcoLRbROxHipwQLEjiQ@mail.gmail.com>
On Sun, 22 Jan 2017 at 23:45:01, Jason A. Donenfeld wrote:
> Nice catch, thanks.
>
> Merged.
Note that I had a similar patch submitted to the mailing list about two
months ago [1] and queued up in lf/for-jason as you told me back then.
Could you check whether the additional changes I have in my version of
the patch are worth applying on top of what we now have in master?
Regards,
Lukas
[1] https://lists.zx2c4.com/pipermail/cgit/2016-November/003431.html
prev parent reply other threads:[~2017-01-23 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 22:30 normalperson
2017-01-22 22:45 ` Jason
2017-01-23 8:38 ` lfleischer [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=148516068856.17037.16353040829889778712@typhoon \
--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).