Sure you can. This is what the svn:externals feature is designed
for. Look up the explanation in the book.
http://svnbook.org
Sent from my iPhone
On Jan 9, 2010, at 6:30 PM, Brian Topping wrote:
You can do that within a single repository, but not between
repositories.
On Jan 9, 2010,
You can do that within a single repository, but not between repositories.
On Jan 9, 2010, at 6:23 PM, Samuel ROZE wrote:
> Hello,
>
> I'm a user of SVN and I want to know if it is possible to create links
> between repositories ?
>
> For exemple, if the directory /project1/trunk/includes/lib1 o
Hello,
I'm a user of SVN and I want to know if it is possible to create links
between repositories ?
For exemple, if the directory /project1/trunk/includes/lib1 of
repository #1 can refer to directory /lib1/trunk of repository #2 ?
[file:///svn/repository-1/projet1/trunk/includes/lib1 ->
file://
On Jan 9, 2010, at 12:58 PM, Rob van Oostrum wrote:
> I see now. The path "/project/!svn" makes no sense. It doesn't exist in the
> repository, so that rule doesn't do anything. The !svn is a SVN-internal
> concept. To assign permissions to /project, you need to have to specify:
>
> [/project]
On 1/9/2010 11:36 AM, David Huang wrote:
On Jan 9, 2010, at 7:58 AM, Geoff Rowell wrote:
I follow a few rules to avoid this:
1) Remove obsolete merge info as part of the branch creation process
(svn pd -R svn:mergeinfo /my/branch).
I don't do that regularly (but have done it once or twice), b
I see now. The path "/project/!svn" makes no sense. It doesn't exist in the
repository, so that rule doesn't do anything. The !svn is a SVN-internal
concept. To assign permissions to /project, you need to have to specify:
[/project]
* = r
Do a search on the old list archives on tigris for some ba
On Jan 9, 2010, at 7:58 AM, Geoff Rowell wrote:
> I follow a few rules to avoid this:
> 1) Remove obsolete merge info as part of the branch creation process
> (svn pd -R svn:mergeinfo /my/branch).
I don't do that regularly (but have done it once or twice), but from my
understanding, that fixes t
Thanks, but that is incorrect. I have no problem downloading sources with a
single rule of "[/project] *=r", nor do I have a problem correctly resolving
group memberships that a user has assigned to them. As well, I have tested
that a user who is not logged in cannot access the repository.
Ar
Your problem is with Crowd, not authz. Authentication is failing: "Could not
authenticate to server: rejected Basic challenge (https://dev.host.net)"
Check your Crowd configuration/documentation. I'd suggest taking SVN out of
the equation and verifying that your integration with Crowd is working
f
