Re: Updating a new branch with existing files from filesystem in 1.7

On Fri, Dec 16, 2011 at 12:53 PM, Adam Walling wrote: > > With 1.6, we would take advantage of being able to copy all of trunk to the > new branch directory on the local filesystem, and then switch to the actual > branch URL and update, therefore only transferring files that actually > differ. Thi

Re: Updating a new branch with existing files from filesystem in 1.7

On Fri, Dec 16, 2011 at 01:53:21PM -0500, Adam Walling wrote: > When creating a new branch, obviously everyone will need to download it for > maintenance and etc. The naive approach is to simply update and download > the new branch from the server. However, with a large branch and with many > users

Re: problem with subversion command: svn propset

On Fri, Dec 16, 2011 at 03:57:14PM +0100, nkr...@gmx.de wrote: > Hello, > > used subversion version: > svn, version 1.6.16 > > Problem: > svn propset fixlog '-r HEAD:23384' . > > Returned error: > svn: Syntax error in revision argument ' HEAD:23384' > > > The problem is the first charcter of t

Updating a new branch with existing files from filesystem in 1.7

When creating a new branch, obviously everyone will need to download it for maintenance and etc. The naive approach is to simply update and download the new branch from the server. However, with a large branch and with many users simultaneously updating, this quickly overloads the bandwidth and may

problem with subversion command: svn propset

Hello, used subversion version: svn, version 1.6.16 Problem: svn propset fixlog '-r HEAD:23384' . Returned error: svn: Syntax error in revision argument ' HEAD:23384' The problem is the first charcter of the property value '-'. It seems that the hyphen '-' is taken as a subversion parameter.

Re: write to svn via https and ssh, svn server with one operating system user for ssh access

On Dec 16, 3:03 pm, Andy Levy wrote: > On Fri, Dec 16, 2011 at 08:56, rupert.thurner > wrote: > > hi, > > > i tried to search a little but i did not see it explicitely: > > > 1. is it possible to access the same svn repository for writing via > > http(s) and ssh? > > Yes. It's in the > manual.h

Re: HowTo upgrade repository from 1.6 to 1.7

On Fri, Dec 16, 2011 at 12:31 PM, Phil wrote: > I've noticed a bug on v1.6 whenever using the svn:// protocol to checkout > numerous files at one time.  I get the svn: compression svndiff failed data > error.  This doesn't occur with v1.7.x > > Therefore, I would like to upgrade to v1.7.  I know I

HowTo upgrade repository from 1.6 to 1.7

I've noticed a bug on v1.6 whenever using the svn:// protocol to checkout numerous files at one time. I get the svn: compression svndiff failed data error. This doesn't occur with v1.7.x Therefore, I would like to upgrade to v1.7. I know I can easily installed the binaries and libraries over v1

Re: why does svn upgrade contact the server?

Am 15.12.2011 15:26, schrieb Jojakim: As I explained in my initial post, we have many individual projects. They are usually not touched - sometimes for years - once they are installed and tested (industrial automation area). When we need to do major changes, yes, we import them in a new repo. But

Re: write to svn via https and ssh, svn server with one operating system user for ssh access

On Fri, Dec 16, 2011 at 08:56, rupert.thurner wrote: > hi, > > i tried to search a little but i did not see it explicitely: > > 1. is it possible to access the same svn repository for writing via > http(s) and ssh? Yes. It's in the manual. http://svnbook.red-bean.com/en/1.7/svn.serverconfig.multi

write to svn via https and ssh, svn server with one operating system user for ssh access

hi, i tried to search a little but i did not see it explicitely: 1. is it possible to access the same svn repository for writing via http(s) and ssh? 2. how would it be possible to configure svn so that only one operating system user is needed for ssh access, like e.g. github is doing? rupert.