[PATCH] hgweb: always start log with searched revision
Kevin Bullock
kbullock+mercurial at ringworld.org
Wed Jul 17 23:19:10 CDT 2013
On 12 Jul 2013, at 6:42 PM, Alexander Plavin wrote:
> # HG changeset patch
> # User Alexander Plavin <me at aplavin.ru>
> # Date 1373668589 -14400
> # Sat Jul 13 02:36:29 2013 +0400
> # Node ID fab1615db25b28837a9af906566c4d8634f06ff8
> # Parent 112ad12761e449b3edaa7bf10caa0b88193ec9fb
> hgweb: always start log with searched revision
>
> This makes the specified revision be always on top of the list.
> Before the patch, for example with repo having revisions 0, 1, 2, 3 and user
> searching for '2', all revisions were shown and the specified one wasn't
> the first.
It took me a while to puzzle out the cause. Is this simply a result of the target rev being too close to the beginning of the repo, so we're showing more revs than we should?
pacem in terris / мир / शान्ति / سَلاَم / 平和
Kevin R. Bullock
More information about the Mercurial-devel
mailing list