I don't deny that clearcase is capable of supporting a number of
branching models :).. What I was saying is that forcing a /0 version on
parent branches can and will cause unnecessary merges( perhaps trivial,
but it's more work still, even more work in cvs for that matter ).
Especially if you are
I'm confused, My understanding is that Rational( or IBM ) recommends a
sparse branching methodology. This methodology is the same one used in
cvs. So the question becomes how are you doing your branching in
clearcase, and what do you consider it's benefits over this methodology?
I'm at a loss
It means that it becomes a requirement to lock the file no matter who
you are.
donald
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marcelo
Carvalho Fernandes
Sent: Friday, May 14, 2004 5:04 PM
To: [EMAIL PROTECTED]
Subject: cvs admin -L
Hi all !
In
Automation isn't really possible, as far as I understand the problem.
There's no way of putting the knowledge of what you want into a
script... And essentially the process centers around moving or renaming
files, it's not terribly difficult to do by hand.
What exactly are you looking for?
-Original Message-
From: Hugh Sasse Staff Elec Eng [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 7:45 AM
To: Paul Sander
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Fouts Christopher (6452);
MKlinke
Subject: RE: Versioning between checkout|update, commit
Thank you for the
The problem with this methodology is that it's very easy for stuff to
get checked in that will break the build for other people. Isolation is
*good*. Allowing people to save work that may not be finished is also
good( although maybe not as good ).
donald
-Original Message-
From:
Yes, please, I can't tell you the hell I've had recently with Timezones
being non-numeric.
Did you know that Australia has a EST timezone that nicely corresponds
to the East coast of the united states?
donald
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
If you never wanted the mp3 file to be in the repository, directly
removing the ,v file is a safe operation to do.
donald
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Fred
Phase
Sent: Tuesday, March 09, 2004 7:28 AM
To: [EMAIL PROTECTED]
Subject: EOF
I'd be carefull about using that line as part of a blind search and
removal.
$Id:.* is very legal syntax with perl code. Having said that a dry run
would
quickly let you know if it was going to cause you problems.
donald
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: CVS Pros/Cons
--- Donald Sharp (sharpd) [EMAIL PROTECTED] wrote:
cut
Check-outs and commits are not atomic. The
repository
will not become corrupt, but if you are checking in
a
number of files and one file fails, the system does
cut
Weaknesses of CVS:
There is no integrity-checking for the source-code
repository. Amazingly, there are no checksums or
signatures to allow the integrity of the source-code
repository to be verified. This means that the
repository can become corrupt and it can be months
before you realize
Andy -
As a suggestion to tackling this problem from a different direction,
would you please
run the check_cvs script over your repository. The script should be
found in the scripts
directory of the cvs distribution. I'm interested in the output.
donald
-Original Message-
From: [EMAIL
12 matches
Mail list logo
