List for cgit developers and users
 help / color / mirror / Atom feed
From: bluewind at xinu.at (Florian Pritz)
Subject: [PATCH] Fix crash when using path limit
Date: Thu, 24 Nov 2016 20:26:57 +0100	[thread overview]
Message-ID: <f3642846-f821-dd3c-01ff-4ed84c578359@xinu.at> (raw)
In-Reply-To: <20161124191659.3694-1-lfleischer@lfos.de>

On 24.11.2016 20:16, Lukas Fleischer wrote:
> The array passed to setup_revisions() must be NULL-terminated. Fixes a
> regression introduced in 455b598 (ui-patch.c: Use log_tree_commit() to
> generate diffs, 2013-08-20).
> 
> Reported-by: Florian Pritz <bluewind at xinu.at>
> Signed-off-by: Lukas Fleischer <lfleischer at lfos.de>

Works perfectly. Thanks!


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 825 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20161124/4aa56cf1/attachment.asc>


  reply	other threads:[~2016-11-24 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 19:16 lfleischer
2016-11-24 19:26 ` bluewind [this message]
2016-11-24 20:29 ` Jason

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=f3642846-f821-dd3c-01ff-4ed84c578359@xinu.at \
    --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).