I found a stray *= in the access folder - dont know how that got there
doh!
On Apr 19, 4:43 pm, Thorsten Schöning wrote:
> Guten Tag coolie,
> am Donnerstag, 19. April 2012 um 17:33 schrieben Sie:
>
> > Is there something I can do on the server to either restore my tags or
> &g
I seem to have lost the tags folder in the repository. I tried to
create a new tag and maybe there was some interruption to the server
or something, but now the whole tags folder is gone!
If I try to re-create in repo-browser or add from the disk I get
access denied.
Is there something I can do o
I found out that I need to use --set-depth to make the depth stick, so
solved this one. Just setting --depth is ignored on the next update.
On Apr 19, 2:50 pm, Johan Corveleyn wrote:
> On Thu, Apr 19, 2012 at 2:42 PM, coolie wrote:
> > Specifiyinfg 'immediates' or 'file
I need to install this functionality for Apache, but I don’t have apxs
and can't find a 64 bit version. Seems like I would also need Perl.
Does anyone know where to obtain apxs for 64 bit Windows?
Alternatively is there a Windows 64 pre-compiled version of
mod_dontdothat?
Specifiyinfg 'immediates' or 'files' does not checkout the externals
for a folder with this property set.
If you then do a checkout with 'infinity' you get the libs, but
subsequent updates delete the lib again!. I can't seem to stop this
behavior now as no matter what I do the lib always gets dele
May have given the wrong impression here - its not access control but just
limiting the depth of checkout to folders matching the list.
On Thursday, 29 March 2012 12:49:57 UTC+1, Nico Kadel-Garcia wrote:
>
> On Thu, Mar 29, 2012 at 7:19 AM, Paul Coulson wrote:
>
>> I have a legacy repo structure
I have an inherited repo structure that has many projects with their own
tags and branches folders.
Users check out the whole structure as there are common lib references etc,
but don't need to see the full contents
of tags or branches folders, which can be massive. I would like a property
svn:i
I have exactly the same issue - I want to inhibit checkout of all tags (and
branches) folders, but still be able to do an update from the root. I've
read the replies on this post and none seem to solve the problem. Did you
find a simple solution? Ideally this should be a property set on the roo
is is not fixed then every user has to edit user specific VS settings
whenever my project is checked out by them. The settings are then wrong for
everybody else when it gets checked back in!
On Monday, 12 December 2011 13:04:47 UTC, Philip Martin wrote:
>
> coolie writes:
>
> > I a
