Vote #63229
完了Mercurial : Don't browse latest version after a 'hg push'
0%
説明
Hello,
the Mercurial adapter use @hg locate@ to get entries from a hg repository. However, @hg locate@ works on the working copy and so needs an updated working copy.
After an @hg push@ from my local clone to the one use by redmine on a server, the working copy on the server is not updated so changesets are fetched but can't be browsed.
A call to @hg update@ while fetching changesets could solve this in my case because it is sort of a central repository used only for pushing pulling and backup. But if someone use redmine on the repository he is working on, an @hg update@ might not be the best thing to do.
Maybe there could be an option to automatically update the working copy while fetching changesets ?
journals
I proposed a patch (#1199) that improves the Mercurial adapter. It also permits to browse a repository independently of its local state. No need to update the working directory as suggested by Frédéric. The trick is to use the <code>-r tip</code> option (<code>hg locate -r tip</code>).
--------------------------------------------------------------------------------
I confirm latest patches from #1199 solve this issue.
--------------------------------------------------------------------------------
I think you can stay issue open as the patch is not included in the official repository.
--------------------------------------------------------------------------------
I marked it 'Resolved' to show that a solution has been found and point to the patch, but it is not closed. It still apears in 'Open Defects'.
If the latest patch works also for you, I think it could be included.
--------------------------------------------------------------------------------
Patch #1199 is applied in r1499.
--------------------------------------------------------------------------------
related_issues
relates,Closed,1199,Mercurial adapter