http + ssh
svn co svn+ssh://your.remote-server.com/home/svn/test is there a way to do something like this but without running subversion daemon, because in my case I use svn through apache? but I need to use SSH as well so somehow http+ssh ? -- http://alexus.org/
fine
is there a way to restrict users to commit only to a /branches vs /trunk? -- http://alexus.org/
Re: fine
ok, path based authentication how would I accomplish that? I'm using apache for svn, I'm not using svnserve On Thu, Jun 2, 2011 at 4:17 PM, Bob Archer wrote: > >> is there a way to restrict users to commit only to a /branches vs > >> /trunk? > > > Two ways.. > > > > 1. Path based authentication... don't give them write access. > > of course I meant path based authorization here. I would like to the book > here, but it doesn't seem to be coming up. > > > > > 2. Pre-commit hook... have the hook not allow commits to /trunk (or > > course you will need a way around the hook.) > > > > BOb > > -- http://alexus.org/
recommiting already commited files
i have this issue here i was wondering if someone can give me a hand... basically i'm running svn server and long story short, we had to restore some backups but here is a tricky part... the backup that we restore isn't latest they are a day old, but clients who's using that svn server is in the future commits vs what svn server has what's the best way to deal with this situation? how do clients recommit stuff to svn server? -- http://alexus.org/
