List for cgit developers and users
 help / color / mirror / Atom feed
From: konstantin at linuxfoundation.org (Konstantin Ryabitsev)
Subject: RFE: changelog between two revisions
Date: Tue, 24 Jul 2018 15:36:42 -0400	[thread overview]
Message-ID: <20180724193642.GB8278@chatter> (raw)
In-Reply-To: <20180724193345.GA7038@john.keeping.me.uk>

On Tue, Jul 24, 2018 at 08:33:45PM +0100, John Keeping wrote:
>On Tue, Jul 24, 2018 at 03:14:49PM -0400, Konstantin Ryabitsev wrote:
>> A very minor feature request -- it would be nice if there was a way to
>> limit /log/ view to only changes between two revisions. In other words,
>> I was looking for a way to replicate this file:
>>
>> https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.17.8
>>
>> using the /log/ view, but there's no way to tell it "stop when you reach
>> tag v4.17.7":
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v4.17.8&showmsg=1
>
>Something like this?
>
>https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?qt=range&q=v4.17.7..v4.17.8&showmsg=1
>
>(although that's a poor example since v4.17.8 only contains a single
>patch, this is perhaps clearer:
>
>https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?qt=range&q=v4.17.8..v4.17.9&showmsg=1
>)

Oh, sweet! I guess I should have looked in the dropdown.

Thanks, John!

-K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20180724/999d9189/attachment.asc>


      reply	other threads:[~2018-07-24 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 19:14 konstantin
2018-07-24 19:33 ` john
2018-07-24 19:36   ` konstantin [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=20180724193642.GB8278@chatter \
    --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).