The standard Python pre-commit hook that comes with Subversion's
source tarball will do the job. I have a Perl version that does the
same thing.
Both of these not only will allow you to keep certain people out of a
branch, but can tag a directory as "add-only". That is, you can "add"
to a director
Our repositories lives in /var/lib/svn/ on a Linux server. We use the
following sturcture on per project per repository basis:
/var/lib/svn/projectA/tags/
/var/lib/svn/projectA/trunk/
/var/lib/svn/projectA/branches/
/var/lib/svn/projectB/tags/
/var/lib/svn/projectB/trunk/
/var/lib/svn/projec
On Mon, Oct 11, 2010 at 4:25 PM, Bernd May wrote:
> Hey all,
>
> I have a curious problem that I seem unable to find precedence for.
>
>
> The Error:
>
> --- on the client side ---
> svn up
> svn: OPTIONS of 'https:///svn/': SSL
> handshake failed: SSL alert received: Decode error (https://)
>
> -
On Mon, Oct 11, 2010 at 14:49, Jeff Avella (Coresoft)
wrote:
> Hi,
>
> I am having a problem getting my comment logs to show up, my files all get
> committed fine but the log comment doesn't show up. Any ideas how to fix
> this?
How are you checking this? Where are the comments not appearing? If
Hi,
I am having a problem getting my comment logs to show up, my files all get
committed fine but the log comment doesn't show up. Any ideas how to fix this?
Thanks
Jeff Avella
Coresoft, Inc.
949-206-0636 x211
jave...@coresoft.com
Ah, sorry, you're right. I remembered "svn mkdir", not "svn add". "svn
add" requires the local content to actually load the file.
On Mon, Oct 11, 2010 at 2:04 PM, Stefan Sperling wrote:
> On Mon, Oct 11, 2010 at 07:25:57AM -0400, Nico Kadel-Garcia wrote:
>> It's also possible to to "svn add
>
On Mon, Oct 11, 2010 at 07:25:57AM -0400, Nico Kadel-Garcia wrote:
> It's also possible to to "svn add
> svn://hostname/reponame/trunk/filename.txt", or whatever the URL would
> be on the Subversion server. In that case, it won't appear locally
> until you do an "svn update" in the local working re
Le 10/10/2010 22:17, Nico Kadel-Garcia a écrit :
On Sat, Oct 9, 2010 at 3:05 PM, jehan procaccia wrote:
Le 09/10/2010 20:40, Nico Kadel-Garcia a écrit :
svn+ssh is the most secure, but it conflcts with your desire for LDAP
access. The SSH keys normally live under a single user's account, the
Hey all,
I have a curious problem that I seem unable to find precedence for.
The Error:
--- on the client side ---
svn up
svn: OPTIONS of 'https:///svn/': SSL
handshake failed: SSL alert received: Decode error (https://)
--- on the server side from apache error.log ---
[debug] ssl_engine_kerne
On Sun, Oct 10, 2010 at 4:26 PM, Les Mikesell wrote:
> On 10/10/10 3:12 PM, Nico Kadel-Garcia wrote:
>>> If they didn't, it would be impossible to do automated commands. There
>>> are
>>> times when you have to choose between trusting the OS to protect your
>>> files
>>> (which is, after all, on
On Sat, Oct 9, 2010 at 1:26 PM, Richard England wrote:
> On 10/09/2010 09:23 AM, 肖晗 wrote:
>
> I am just new to subversion and encountered some confusion.
> I have set up a svn server on my ubuntu/linux.
> After creating an account called "test" under /var/svn(using svnadmin create
> /var/svn/test
11 matches
Mail list logo