Log view URL parameter to mark / highlight changesets

[anonymous]

We use Trac to review "PR" branches. We write a ticket comment like this

Proposed changes in log:jomae.git@t13567 (1 commit)

This works fine for 1 or 2 commits, but for larger branches it is difficult to see (count) what commits are relevant.

Feature request: Allow somehow appending a parameter like ?commits=1-14:

Proposed changes in log:jomae.git@t13567?commits=1-14

This would be similar to the ?marks=1-14 appended by source:jomae.git/.github/workflows/build-completed.yml@t13567:1-14​ and similarly highlight the first 14 commits / rows in the log table.

[anonymous]

log:jomae.git@27971c89:t13567 is an almost similar existing feature, but has downsides that make it unusable:

• You have to lookup the start commit hash 27971c89.
• You can not write e.g. log:jomae.git@t13567^14:t13567 and even that would be very inconvenient with the repeated branch name, especially when using longer branch names.
• You don't see the other rows at all.

[Jun Omae]

How about log:jomae.git@trunk:t13567 ?

[anonymous]

It doesn't work on our Trac. (No changeset trunk in the repository.) What is trunk there? Is it a Git concept? (We use Mercurial.)

[Jun Omae]

You could use the following links:

• View logs from branch1 through branch2 - log:<reponame>@<branch1>:<branch2>
  • e.g.
    • log:jomae.git@trunk:t13567
    • log:jomae.hg@6ec290a4d658:trunk
• View logs at most N revisions - log:<reponame>@<branch>?limit=<N>
  • e.g.
    • log:jomae.git@t13567?limit=7
    • log:jomae.hg@trunk?limit=7

[anonymous]

Thanks for the feedback. &limit=... is a good option.

I still don't understand the trunk trick. What is trunk there? Is it Git specific? Is there a Mercurial equivalent? Thanks.

[Jun Omae]

I still don't understand the trunk trick. What is trunk there? Is it Git specific? Is there a Mercurial equivalent? Thanks.

No. That is not trick. Specify existent branches/tags/sha-hahses in your repository to branch1 and branch2 in log:<reponame>@<branch1>:<branch2>.

[anonymous]

I see, thanks, so trunk is the branch name, specific to the SVN-converted-to-Git Trac repository that points to the start of the relevant changes.

For a pure Mercurial repository we would need revsets, log:<reponame>@<revset1>:<revset2>, but that doesn't seem to work.

[Jun Omae]

For a pure Mercurial repository we would need revsets, log:<reponame>@<revset1>:<revset2>, but that doesn't seem to work.

Ah, that is probably caused by log view for Mercurial repository listing by integer revision numbers.

Relative issues: #13092, #13318