From: mricon at kernel.org (Konstantin Ryabitsev)
Subject: [PATCH 0/4] Add "stat only" diff mode
Date: Mon, 06 Oct 2014 09:25:16 -0400 [thread overview]
Message-ID: <5432983C.5020402@kernel.org> (raw)
In-Reply-To: <20141006061046.6337.1007@typhoon.lan>
On 06/10/14 02:10 AM, Lukas Fleischer wrote:
> On Mon, 06 Oct 2014 at 05:01:41, Jason A. Donenfeld wrote:
>> Curious to know the motivation behind this patchset. Why would you want
>> stat-only?
>> [...]
>
> To avoid loading the whole diff when you're only interested in changes
> to a single file [1].
>
> [1] http://lists.zx2c4.com/pipermail/cgit/2014-September/002235.html
\o/
Yes, to use a more relevant example, we get quite a bit of traffic to
the following page:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/diff/?id=v3.17&id2=v3.16
(warning, trying to load it may kill your browser)
However, people are only interested in seeing diffs to specific drivers
or submodules, not the whole thing. Generating the whole diff 3.17-3.16
is pretty much useless to anyone not certifiably insane, and it eats up
a ton of traffic for no purpose. Having the ability to only display
diffstat would be extremely handy.
Best,
--
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montr?al, Qu?bec
prev parent reply other threads:[~2014-10-06 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 9:59 john
2014-10-05 9:59 ` [PATCH 1/4] ui-shared: remove toggle_ssdiff arg to cgit_commit_link() john
2014-12-24 1:48 ` Jason
2014-10-05 9:59 ` [PATCH 2/4] ui-shared: remove toggle_ssdiff arg to cgit_diff_link() john
2014-12-24 1:49 ` Jason
2014-10-05 9:59 ` [PATCH 3/4] Change "ss" diff flag to an enum john
2014-12-24 1:49 ` Jason
2014-10-05 9:59 ` [PATCH 4/4] ui-diff: add "stat only" diff type john
2014-12-24 1:49 ` Jason
2014-10-06 3:01 ` [PATCH 0/4] Add "stat only" diff mode Jason
2014-10-06 6:10 ` cgit
2014-10-06 13:25 ` mricon [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=5432983C.5020402@kernel.org \
--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).