subpaths seems to malfunction

[jamesm]

I have a repository with a number of subpaths in the .hgsub file. These are used to redirect the repositories from being nested to flat when pushing to hosted services.

I have number of rules under the [subpaths] section of the file such as this:

[subpaths]
http://(.*)/parentRepo/Game = http://\1/parentRepogame

However when I try to commit the parentRepo in sourcetree it seems to recognize these subpath rules as real repositories ( http://(.*)/parentRepo/Game is listed as a sub repository for example) for the sake of committing and will not let me commit parentRepo until the other (non existant) repos have been commited.

Am I using source tree incorrectly or is this a bug?

Regards,

James Mintram

[stevestreeting · Accepted solution]

This is probably technically a bug, but I must admit to not understanding the intention or expected behaviour of a setup like this - SourceTree's support for subrepositories has primarily been designed with linked sub-projects in mind (similar to svn externals etc).

Can you explain the purpose & expected behaviour of your case or point me to some documentation that illustrates it? I don't understand how these subpaths can be non-existent as you refer to them.

[jamesm]

Hi Steve,
Here is a link that explains properly what I am doing with sub repos: http://mercurial.selenic.com/wiki/SubrepoRemappingPlan

So on services like Bitbucket that only allow flat repository names such as http://bitbucket.org/user/repository_subrepo and not http://bitbucket.org/user/repository/subrepo I can use the remapping ability in the .hgsub file

I hope that better explains it :)

Is this likely to get fixed?

Regards,

James Mitnram

[stevestreeting]

Thanks for the info - I'm tracking this issue in my work queue here: https://jira.atlassian.com/browse/SRCTREE-954

It'll definitely get fixed; I'll try to get it at least tolerating this setting in a 1.4 point release, the next one if possible (although that's due tomorrow!)

[stevestreeting]

It appears to be a trivial change to tolerate this configuration actually, please can you try this pre-release build and let me know if it solves your issue?

http://downloads.atlassian.com/software/sourcetree/SourceTree_test.zip

[jamesm]

Yeah, that appears to work brilliantly! Thanks very much for the quick update to the app :) Regards, James Mintram

[stevestreeting]

Awesome, this will be in the official 1.4.3 update. Thanks for testing.