Subversion subrepositories and revisions stored in .hgsubstate

Oleg Stepanov oleg.stepanov at jetbrains.com
Wed Jan 19 07:07:23 CST 2011


I believe that since svnsubrepo is implemented through command-line
interface to SVN, the best way is to invoke 'svn info' in the subrepo
context and parse revision number after 'Last Changed Rev:'.
--
Oleg Stepanov, JetBrains
"Develop with pleasure!"
olegstepanov.livejournal.com (Rus) | @olegstepanov | skype:oleg.stepanov



On Wed, Jan 19, 2011 at 1:38 PM, Martin Geisler <mg at aragost.com> wrote:
> Oleg Stepanov <oleg.stepanov at jetbrains.com> writes:
>
>> Hi,
>>
>>   Why does hg store revision number for svn subrepositories in
>> .hgsubstate instead of last changed revision for the actual svn path?
>> The way it currently is .hgsubstate updates more frequently than
>> needed which results in excess commits.
>
> I guess nobody has thought about this before you... since Mercurial does
> not support partial checkouts, storing the repository-wide changeset ID
> makes sense for Mercurial subrepos, but with Subversion you can indeed
> get unnecessary commits to the .hgsubstate file if you only checkout a
> subtree of your Subversion repository.
>
> I think we can fix this if you come up with a way to query SVN for when
> a subtree was last touched.
>
> --
> Martin Geisler
>
> aragost Trifork
> Professional Mercurial support
> http://aragost.com/en/services/mercurial/blog/
>
> !DSPAM:19,4d36db5d76851189034578!
>
>


More information about the Mercurial-devel mailing list