svn handles symlinks by having a special file attribute for “this is a
symlink” and the contents in its repository are just the directory to point
the symlink at.
This works well for simple cases, although I’ve found replacing symlinks
with real files can cause some confusion if you’re not careful
For me the key differences between git and svn come down to development
model. In general, they can both be made to do the same things and which is
easier to “bend to your will" comes down to how you prefer to work.
If you have a defined group of people working on a project, and want to have
a sin
You can’t put in arbitrary wildcards, but you don’t have to specify a
repository.
If you use one project per repository (which I highly recommend), then you
can just define
[/trunk/passwords]
*=
or similar to set up permissions for the same path in all projects.
— Sarah
Codesion.com
On 21 M
As others have said, it sounds like there is a file in your repository
with some characters in the filename that your OS doesn't like. The
best fix is to find and rename the file. Here are some suggestions on
how to do this if you're having trouble just checking it out.
A checkout should tell you
Hi,
I was looking at the cool stuff you can do with apache's repository replication
& write-through proxy options, and thinking "wow I wonder if there's an easy
way to run something like this locally, so I can have lightning fast access to
my regularly used svn repositories?"
Is this somethin
