On Sat, Apr 17, 2010 at 16:58, Rainer Dorsch rdor...@web.de wrote:
and a more recent version in a non-standard dir (which is added to my path
in .bash_profile)
add it to your path in .bashrc instead. .bash_profile only gets loaded
by interactive login shells.
I expect that .bash_profile is
B Smith-Mannschott wrote on Mon, 19 Apr 2010 at 08:08 +0200:
On Sat, Apr 17, 2010 at 16:58, Rainer Dorsch rdor...@web.de wrote:
and a more recent version in a non-standard dir (which is added to my path
in .bash_profile)
add it to your path in .bashrc instead. .bash_profile only gets
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
have you looked into svn:externals
On 19 April 2010 08:41, ja...@smars.pl 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
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
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
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
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 projects are in
Rob van Oostrum wrote:
On Fri, Apr 16, 2010 at 2:21 PM, J. Norment jnorm...@q2software.com
mailto: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 weeks since
the last
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. 6
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
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
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-time
On Mon, Apr 19, 2010 at 15:14, Vikrama Sanjeeva viki.sanje...@gmail.com 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
On Mon, Apr 19, 2010 at 3:14 PM, Vikrama Sanjeeva
viki.sanje...@gmail.comwrote:
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
On Mon, Apr 19, 2010 at 3:29 PM, KARR, DAVID (ATTSI) dk0...@att.com 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
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 could
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
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 result in
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:
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.
In cvs:
21 matches
Mail list logo
