On Thu, Jul 04, 2013 at 15:56:45 +0200, Johan Corveleyn wrote:
> Beware though that post-commit hooks may be running concurrently, and
> your 'svn update' launched by $REV might still be running when $REV+1
> tries to start 'svn update'.
I can see that it could be a problem. Not for us in this cas
Hi Johan,
Thank you for your quick response!
On Thu, Jul 04, 2013 at 15:18:57 +0200, Johan Corveleyn wrote:
> > We have a svn repository with many files (more than 30'000), and need to
> > have the HEAD version exported to a filesystem, whenever a commit is
> > done.
> > ...
>
> First thing to ch
Hi,
We have a svn repository with many files (more than 30'000), and need to
have the HEAD version exported to a filesystem, whenever a commit is
done.
Currently, we have implemented this with a post-commit script that does
a "svn update", but the script is rather slow. The reason is that "svn
up
t svnserve 1.7 considers the argument to
check-path relative to the URL that was used to connect, whereas
svnserve 1.6 considered it absolute to the repository.
Can you confirm this? Is it a problem in Subversion or Svnkit?
Thank you and cheers
David Schweikert
4 matches
Mail list logo