From: tim.nordell at logicpd.com (Tim Nordell)
Subject: [PATCH] ui-diff: Add configuration option to limit number of files
Date: Mon, 29 Feb 2016 14:48:15 -0600 [thread overview]
Message-ID: <56D4AE8F.9040402@logicpd.com> (raw)
In-Reply-To: <20160228123848.GX1766@serenity.lan>
On 02/28/16 06:38, John Keeping wrote:
> I wonder if people will miss the fact that the diff stat has been
> truncated. Would it be better to just drop the entire thing if there
> are too many changed files and replace it with something like:
>
> This diff is really big, are you sure you want to see it?
>
> and provide a link that bypasses this limit?
>
Good idea. What if the diffstat is truncated, and rather than showing
any diffs, it shows the message above? It's still sometimes useful to
see a snippet of what changed even if it's huge. I suppose maybe the
"forced" view could be a link to downloading the patch locally?
There are circumstances in which I really don't want an HTML view of the
full changeset to ever be rendered to someone remotely. An extreme
example of this is when the kernel tree was introduced (commit tagged
v2.6.12-rc2 in any CGIT hosted kernel repo). I won't link it here, but
it takes well over 100 seconds to generate on kernel.org's server, and
content-wise is well over 300MiB since it contains essentially the
entire source code of kernel v2.6.12-rc2 in HTML form since it was the
introduction commit to the kernel.
- Tim
prev parent reply other threads:[~2016-02-29 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 20:57 tim.nordell
2016-02-28 12:38 ` john
2016-02-29 20:48 ` tim.nordell [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=56D4AE8F.9040402@logicpd.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).