From: mricon at kernel.org (Konstantin Ryabitsev)
Subject: Bug: rawdiff output truncated on cache save
Date: Mon, 24 Apr 2017 11:54:40 -0400 [thread overview]
Message-ID: <20170424155440.GB15623@gmail.com> (raw)
Hello, all:
Very reminiscent of a fix for ui-patch.c that fixed patch truncation [1]
there's a similar problem with cached rawdiff output. E.g.:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/rawdiff/?id=v4.11-rc7&id2=v4.11-rc8
You will notice that the output is truncated (if it isn't just reload to
get the cached version).
I would love a speedy fix, as we're trying to use this in place of
publishing pre-generated patches.
Best,
-Konstantin
[1] https://git.zx2c4.com/cgit/commit/?id=2efb59ed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20170424/eba0c8be/attachment.asc>
next reply other threads:[~2017-04-24 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 15:54 mricon [this message]
2017-04-24 18:52 ` [PATCH] cache: flush stdio before restoring FDs john
2017-04-24 18:55 ` Jason
2017-04-28 16:36 ` mricon
2017-09-25 12:51 ` mricon
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=20170424155440.GB15623@gmail.com \
--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).