Re: Help

On Apr 19, 2010, at 5:50 PM, Ryan Schmidt wrote: > > On Apr 19, 2010, at 17:39, Ryan Schmidt wrote: > >> On Apr 19, 2010, at 17:04, Omar Ousmane Kadry wrote: >> >>> Not sure if it is the right place for this but I’m looking for a way to >>> imitate the cvs behavior when checking out folders.

Re: Help

On 4/19/2010 5:39 PM, Ryan Schmidt wrote: On Apr 19, 2010, at 17:04, Omar Ousmane Kadry wrote: Not sure if it is the right place for this but I’m looking for a way to imitate the cvs behavior when checking out folders. In cvs: cvs co mod1/dir1/dir2/file2 will result in having: m

Re: Help

On Apr 19, 2010, at 17:39, Ryan Schmidt wrote: > On Apr 19, 2010, at 17:04, Omar Ousmane Kadry wrote: > >> Not sure if it is the right place for this but I’m looking for a way to >> imitate the cvs behavior when checking out folders. >> In cvs: >>cvs co mod1/dir1/dir2/file2 >>will resul

Re: Help

On Apr 19, 2010, at 17:04, Omar Ousmane Kadry wrote: > Not sure if it is the right place for this but I’m looking for a way to > imitate the cvs behavior when checking out folders. > In cvs: > cvs co mod1/dir1/dir2/file2 > will result in having: > mod1/dir1/dir2/file2 > > How can I

Help

Hi, Not sure if it is the right place for this but I'm looking for a way to imitate the cvs behavior when checking out folders. In cvs: cvs co mod1/dir1/dir2/file2 will result in having: mod1/dir1/dir2/file2 How can I obtain this hierarchical checkout with SVN? Thanks

Re: How to get list of valid revision numbers for an element?

On 4/19/2010 4:31 PM, Ryan Schmidt wrote: On Apr 19, 2010, at 14:55, David Weintraub wrote: On Mon, Apr 19, 2010 at 3:29 PM, KARR, DAVID (ATTSI) wrote: I'm considering writing a script which (among other things) can iterate through all the valid revisions for an element. I'm trying to figure o

Re: svnsync isn't working

On Mon, Apr 19, 2010 at 11:46 AM, J. Norment wrote: > Rob van Oostrum wrote: > > On Fri, Apr 16, 2010 at 2:21 PM, J. Norment > jnorm...@q2software.com>> wrote: >> >> >>Is anyone seeing this message that has any ideas how to fix this? ( >> This message is a repeat. ) It's now been about 3

Re: How to get list of valid revision numbers for an element?

On Apr 19, 2010, at 14:55, David Weintraub wrote: > On Mon, Apr 19, 2010 at 3:29 PM, KARR, DAVID (ATTSI) wrote: >> I'm considering writing a script which (among other things) can iterate >> through all the valid revisions for an element. I'm trying to figure >> out the best way to do that. I coul

Re: How to get list of valid revision numbers for an element?

On Mon, Apr 19, 2010 at 3:29 PM, KARR, DAVID (ATTSI) wrote: > I'm considering writing a script which (among other things) can iterate > through all the valid revisions for an element. I'm trying to figure > out the best way to do that. I could easily just start at "1" up to the > latest revisio

Re: fixing bug in multiple releases

On Mon, Apr 19, 2010 at 3:14 PM, Vikrama Sanjeeva wrote: > Suppose I have total 6 releases in /tag which are considered as stable > releases. Now if, at 6th release we realize that there is a "bug" which > should be fixed in all previous releases then what should be the strategy ? > Is there any w

How to get list of valid revision numbers for an element?

I'm considering writing a script which (among other things) can iterate through all the valid revisions for an element. I'm trying to figure out the best way to do that. I could easily just start at "1" up to the latest revision number, and just check for errors on each one, but that seems pretty

Re: fixing bug in multiple releases

On Mon, Apr 19, 2010 at 15:14, Vikrama Sanjeeva wrote: > Hi, > >    Suppose I have total 6 releases in /tag which are considered as stable > releases. Now if, at 6th release we realize that there is a "bug" which > should be fixed in all previous releases then what should be the strategy ? > Is th

fixing bug in multiple releases

Hi, Suppose I have total 6 releases in /tag which are considered as stable releases. Now if, at 6th release we realize that there is a "bug" which should be fixed in all previous releases then what should be the strategy ? Is there any way in SVN which allows to fix bug in all releases "at-a-ti

blocking merges and branches

I have two special files. One I would like never to be merged. The other I would like to only ever exist in trunk. Is there any mechanism to accomplish this? If you careThe file I don't want to merge contains the version numbers for products built in that branch and the un-branchable file is

Corrupted FSFS commit - possible bug in subversion 1.6.5?

Hi, we encountered (again) the error already discussed in the earlier thread "Corrupted FSFS commit" (starting February 25). When checking out a reporitory from a subversion 1.6.5 server via https (apache 2.2), a client receives a connection abort. The log file states "Svndiff contains a too-

Re: svn+ssh: Expected FS format '2'; found format '4'

Am Monday 19 April 2010 08:08:48 schrieb B Smith-Mannschott: > > I expect that .bash_profile is not executed when I do svn+ssh, but it is > > when I do ssh into the host regularly. > > Yup. But .bashrc should be sourced in both cases. Worked well, many thanks. Rainer -- Rainer Dorsch Lärchenstr

Re: svnsync isn't working

Rob van Oostrum wrote: On Fri, Apr 16, 2010 at 2:21 PM, J. Norment > wrote: Is anyone seeing this message that has any ideas how to fix this? ( This message is a repeat. ) It's now been about 3 weeks since the last replication / backup. The rep

Re: Is there a simple log/diff frontend (like gitk)?

yes, the guys are right, you probably need to update your WC. this is feature, not a bug. some svn clients do not behave this way, like ms-windows tortoise. for mac, i recommended a friend of mine smartsvn, he quite enjoyed it. works for windows too, it is probably written in java. my friend was q

Re: Extra newline added to commit messages -- why?

On Friday 16 April 2010, Ori Avtalion wrote: > [...] I realized that the commits I saw without the extra newline > were either made by "commit -m", git-svn, or by removing the helper > "--This line, and those below, will be ignored--" text from the > commit message file and telling the editor to no

Re: Question about auto commit

On Apr 19, 2010, at 04:36, ja...@smars.pl wrote: >>> when I commit changes on either trunk, this change is made only on >>> /share/module_1234 (the revision number of project1 or project2 will not >>> increase). >> >> I guess you have each project in its own repository? Ok. > > Actually all pro

Re: Question about auto commit

> > On Apr 19, 2010, at 03:53, ja...@smars.pl wrote: > >> Ok, it seems to be ok but has some disadvantages: >> >> when I commit changes on either trunk, this change is made only on >> /share/module_1234 (the revision number of project1 or project2 will not >> increase). >> Because of the above th

Re: Question about auto commit

On Apr 19, 2010, at 03:53, ja...@smars.pl wrote: > Ok, it seems to be ok but has some disadvantages: > > when I commit changes on either trunk, this change is made only on > /share/module_1234 (the revision number of project1 or project2 will not > increase). > Because of the above there is no i

Re: Question about auto commit

Ok, it seems to be ok but has some disadvantages: when I commit changes on either trunk, this change is made only on /share/module_1234 (the revision number of project1 or project2 will not increase). Because of the above there is no information in show log of project1/project2. The trunk history

Re: Question about auto commit

The SVN solution for this use case svn:externals ([1]). Basically, you would have a single instance of module_1234: /share/module_1234 and in each project you use that module, you define the svn:externals property to point to that module: /project1/trunk - svn:externals = ^/share/module_1234 module

Re: Question about auto commit

have you looked into svn:externals On 19 April 2010 08:41, wrote: > hello > > I have a situation, where there are two(or more) projects with its trunks, > and some modules in these trunks are the same: > > /project1 > /project1/trunk > /project1/trunk/module_123 > /project1/trunk/module_1234 > /

Question about auto commit

hello I have a situation, where there are two(or more) projects with its trunks, and some modules in these trunks are the same: /project1 /project1/trunk /project1/trunk/module_123 /project1/trunk/module_1234 /project1/trunk/module_12345 /project1/trunk/module_4567 /project2 /project2/trunk /pro