From: john at keeping.me.uk (John Keeping)
Subject: Truncate "commit" page
Date: Thu, 8 Sep 2016 12:19:03 +0100 [thread overview]
Message-ID: <20160908111903.GE8854@john.keeping.me.uk> (raw)
In-Reply-To: <CALPT=gzS1AXT_fGYG=heCnm9ipjNoGFRxaB300SsP5xPemZheQ@mail.gmail.com>
On Thu, Sep 08, 2016 at 07:11:38AM +0000, Luc Chante wrote:
> It's not exactly what I'm looking for, but I will try this.
Yeah, I didn't think it would be exactly what you wanted but it's the
closest we have at the moment.
I think there are two small improvements which would make it much more
usable:
1) Add a link to get from stat-only mode to the full diff
2) Add a configuration variable to use stat-only mode by default
Would that get closer to what you're looking for or is there something
still missing?
> Le mer. 7 sept. 2016 ? 14:58, John Keeping <john at keeping.me.uk> a ?crit :
>
> > On Wed, Sep 07, 2016 at 11:44:30AM +0000, Luc Chante wrote:
> > > I wonder if there is a way to truncate the content of the "commit" page ?
> > >
> > > I have heavy commits (like adding dependencies when using npm modules).
> > > Beside the fact that the log is quite unusable, the rendered page can be
> > > massive and very long to receive and/or to display.
> >
> > I think you should be able to add "dt=2" to the query parameters in the
> > URL to enable the "stat only" diff mode, but it looks like we don't have
> > a way to enable that by default via the config.
> >
> > The feature was originally added to support links to diffs between Linux
> > kernel versions (e.g. for the patch from v4.4.18 to v4.4.19) and it
> > hasn't been extended at all beyond that, but the commit page calls the
> > same code to generate the diff so the query parameter should work there
> > as well.
prev parent reply other threads:[~2016-09-08 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 11:44 luc.chante
2016-09-07 12:58 ` john
2016-09-08 7:11 ` luc.chante
2016-09-08 11:19 ` john [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=20160908111903.GE8854@john.keeping.me.uk \
--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).