Try:
http://www.laine.org:8080/cvs/vss2cvs/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Alex Jacques
Sent: Thursday, October 11, 2001 12:31 PM
To: [EMAIL PROTECTED]
Subject: Anyone have VSS2CVS?
The site for vss2cvs
Are you changing from VSS to CVS? Can you tell me your reasons? I'm trying
to convince here at the company where I work to do the same, so all
arguments I can get are usefull
Thanks in advance
Fernando
-Original Message-
From: Gianni Mariani [SMTP:[EMAIL PROTECTED]]
Sent:
Subject : CVS admin -m : bug ?
Hello,
I don't seem to fully understand the way cvs admin -m works; it is intended
to change a given file revision log message to another.
When I do :
cvs admin -mHEAD:My changed log message file
the actual log found in the repository file,v is just My, the
Hi!
The 1.1.1.1 version number is a an internal CVS feature having to do
with vendor branching. Your newly imported files have both a 1.1 and
a 1.1.1.1 revision number. Don't worry about it, when you commit new
versions to these files, they will go to 1.2, and the next
vendor import will go
... easy on me, CVS Newbie!! :-)
Hi,
This is probably a silly permission error problem, but can't figure it out:
I've installed CVS following the HOWTO tutorial under linux (RH6.1).
It installed fine (v 1.10.6). However, when I try and import a source
tree with the cvs import command, I
Kaz Kylheku wrote:
CVS doesn't require hand merging. When you perform a cvs update
operation, then new changes in the repository are automatically
incorporated into your working copy. Only when a conflict arises do
you have to do resolution by hand. Conflicts tend to occur rarely, and
are
Freedom? What freedom? Is it not source control or is it source freedom?
One is free to more easily and quickly lay waste to another's work, but that's
hardly an improvement.
CVS smells just like what it is, an acedemic exercize. I've used all manner of
them over the years: PostgreSQL,
Hi,
I have 2 repositories (say A and B). A file is common to both these
repositories.
This file is undergoing simultaneous modifications (independently checked
out from both the repositories). I need to merge both the modifications.
I tried to move the file from repository A to the relevent
James Knowles wrote:
now if I can just add locking to CVS
Try understanding client-oriented parallel development. It will cause less
heartburn, reduce your stress, and reduce the rate of hair loss.
None of these problems I have. I just don't have time to spend days on a
worthless
Netscape tries and tries, but nothing is ever returned by this link.
Paul Sander wrote:
Ich funde es bei http://sourceforge.net/tracker/index.php?func=detailaid=422733group_id=4680atid=304680
>--- Forwarded mail from [EMAIL PROTECTED]
>Wo? Ich kann nicht es gefunden.
>Paul Sander wrote:
>>
I got the link through clicking. I think you're doing something wrong.
Can you explain all the steps you're taking?
Better yet, I'll tell you how I got to the patches:
1. User your browser to go to http://www.sourceforge.com/
2. Enter RCVS into the search field
3. Click on Renegade CVS
4.
It sounds like the software your group is maintaining needs factoring to
decrease the likelihood that several developers are modifying the same
method. It also sounds like your group can use some communication.
Noel
Greg A. Woods wrote:
Read Berliner's whole paper. Understand what it means
--- Bryon Lape [EMAIL PROTECTED] wrote:
Kaz Kylheku wrote:
CVS doesn't require hand merging. When you perform a cvs update
operation, then new changes in the repository are automatically
incorporated into your working copy. Only when a conflict arises do
you have to do resolution by
If you've really made up your mind then don't use CVS. But think about
this first: Why are you the only group I know who has tried parallel
development and didn't like it?
Noel
*** REPLY SEPARATOR ***
On 11/10/2001 at 23:03 [EMAIL PROTECTED] wrote:
Read Berliner's whole
Then spend time doing the merge by hand and having to
possibly to ahold of the programmer who made other changes to make sure
everything
is done correctly. Now two programmers, at least, are being unproductive
and
costs are going up.
Don't you have regression tests to check if you've broken
Conflicts are extremely easy to produce and may not be easily resolved.
The issue it seems you are having is that on a regular basis, two or more
developers making large abouts of unrelated changes to same sections of
code.
This problem cannot be solved by locking checkouts, or by any change
You need to ask yourself why your group is experiencing so many conflicts
while so many other groups (thousands?) are not.
Noel
Kaz Kylheku wrote:
CVS doesn't require hand merging. When you perform a cvs update
operation, then new changes in the repository are automatically
incorporated
Conflicts are easy to produce *when you have multiple developers working on
the same segments of code*.
If you are doing a lot of that without any coordination between the
developers, you are going to have a lot of problems. Period.
___
Info-cvs
Hello cvs users.
I have following problem.
1. I check out a repository into a temporary directory, edit some files and
do than a commit and a release -d.
2. After that, i try to check out the same repository into another directory
to get the actual files. But i got
following
-Original Message-
From: Bryon Lape [mailto:[EMAIL PROTECTED]]
The benefits add up to zero. Now, if it did method locking,
that would be helpful,
protective AND productive. Without some sort of locking,
having developers waste
time with doing merging by hand is
* In message 6npx7.65227$[EMAIL PROTECTED]
* On the subject of Re: [[EMAIL PROTECTED]: Re: rename in cvs]
* Sent on Thu, 11 Oct 2001 22:50:42 GMT
* Honorable [EMAIL PROTECTED] (Kaz Kylheku) writes:
why can't cvs mv just rename the *,v file?
Because then if you check out (or
We *have* changed to CVS.
Some of the reasons.
- cross platform support (win32/unix/mac)
- has all features we cared about in VSS
- easy remote access
- concurrent model development
- easy handling of branches
- easy merging
- easy to write tools to co-ordinate with bug system - bugzilla
-
GAW == Greg A Woods [EMAIL PROTECTED] writes:
GAW Far worse are operations which add, delete, or move, tags; but as
GAW I've mentioned several times again recently it would be very easy to
GAW add an additional access control for those kinds of things, at least
GAW on a
I've got two top level projects in a single cvs
repository.
I'd like to lock one of those projects. In other
words, I'd like for everyone, except maybe one or two users, to be read only
users of one of the projects. The other projects needs to remain read/write for
all. It looks like I
Dr Jaime V. Miro writes:
According to HOWTO, import is executed as a normal user, whereas $CVROOT
(under which the repository is installed) and files under have got
root permissions only (o/g/u), which is the way it was installed.
I can see why is giving me the permission error, but I did
[EMAIL PROTECTED] writes:
When I do :
cvs admin -mHEAD:My changed log message file
the actual log found in the repository file,v is just My, the first
word of the changed message.
That is a problem with your operating system/command interpreter, not
CVS.
-Larry Jones
The surgeon
[EMAIL PROTECTED] writes:
2. After that, i try to check out the same repository into another directory
to get the actual files. But i got
following messages
cvs checkout: Updating watchdogs
? watchdogs/arrays
? watchdogs/clean_tmps
? watchdogs/diskstat
? watchdogs/fs
[ On Thursday, October 11, 2001 at 20:06:18 (-0700), Paul Sander wrote: ]
Subject: Re: cvs exit status
cvs update
if [ $? -ne 0 ] ; then
echo something bad happened, exit status is $?
fi
exit $?
Neither of our scripts is truly useful because both always
[EMAIL PROTECTED] writes:
Using my script it takes 10 mins to put your system under CVS control.
The learning curve in the simplest case is:
$ su
# cvs-etc
If you're using su to get to root, then CVS should be able to figure out
your real userid and you should be able to
[ On Thursday, October 11, 2001 at 23:16:48 (-0600), James Knowles wrote: ]
Subject: Re: Making a file writeable
I guess it's like freedom. Freedom scares the living daylights out of people
conditioned to living under tight controls.
Very good point.
Some (many? most?) people just aren't
Hi Guys:
I sent and email some weeks ago regarding to cvs co -d . oracle32/make and
the server send me this error
cvs server: existing repository /home/kmcvs/src does not match
/home/kmcvs/src/oracle32
cvs server: ignoring module oracle32/make
I was looking into in the archives files and I saw
[ On Friday, October 12, 2001 at 11:21:03 (GMT), Bryon Lape wrote: ]
Subject: Re: Making a file writeable
Freedom? What freedom? Is it not source control or is it source freedom?
One is free to more easily and quickly lay waste to another's work, but that's
hardly an improvement.
CVS
[ On Thursday, October 11, 2001 at 23:08:38 (-0700), Paul Sander wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
I gain the requirement of having to type multiple cvs log or cvs rlog
commands, after figuring out every place a file has lived during its
lifetime. I gain the
[ On Friday, October 12, 2001 at 11:22:37 (GMT), Bryon Lape wrote: ]
Subject: Re: CVS - setup reserved checkout
Conflicts are extremely easy to produce and may not be easily resolved.
Hmmm. and how is this different from any other change control
process? In non-parallel processes
Hi Larry,
I kinda figured there were a problem with file permissions. To that end, I uninstalled
cvs 1.10 and downloaded and installed 1.11.1p. But this time, I ran the command cvs
init
as a normal user (once the user was added to cvs group) instead of root as suggested
in HOWTO
[ On Friday, October 12, 2001 at 09:35:58 (-0500), Thornley, David wrote: ]
Subject: RE: CVS - setup reserved checkout
What do you mean by method locking? Locking individual parts
of a file? It wouldn't do you any good.
Well, not with CVS anyway! :-)
Maybe in a multi-user smalltalk
Wow, Greg meets his match ...
Bryon,
Consider this:
3 developers (A,B,C) need to fix file X.
A is making some major changes, adding lots of new functionality.
B and C need to make a minor tweak to the file.
In a CVS model:
B anc C can be done and outa there in minutes and essentially forget
On Thu, 11 Oct 2001, Greg A. Woods wrote:
[ On Monday, October 1, 2001 at 09:12:24 (+), Gerhard Ahuis wrote: ]
Subject: Re: Howto solve this in cvs ?
Greg A. Woods [EMAIL PROTECTED] wrote:
For many of the same reasons it's literally impossible to ever have true
multi-vendor
[ On , October 12, 2001 at 10:59:41 (-0400), Sam Steingold wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
I wonder why Greg A. Woods could no say that as a reply to the _first_
message suggesting this.
Because you could have figured this out with only the tiniest amount of
[ On , October 12, 2001 at 11:30:07 (-0400), Jake Colman wrote: ]
Subject: Re: How to lock CVS for check-in
So please explain how you would prevent access to specific branches for
specific users? I'm not sure why you think that this is not a reasonable
thing to want to try to do?
Simply
[ On Friday, October 12, 2001 at 12:12:27 (-0400), Larry Jones wrote: ]
Subject: Re: Why can't root check in files?
If you're using su to get to root, then CVS should be able to figure out
your real userid and you should be able to commit. If not, you need to
figure out why getlogin()
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 12, 2001 9:11 AM
[ On Thursday, October 11, 2001 at 20:06:18 (-0700), Paul
Sander wrote: ]
And your point is what? That it's okay to sometimes let
nondeterministic
errors go undetected? Sorry, that's not good
[ On Friday, October 12, 2001 at 10:35:16 (+0200), Gerhard Ahuis wrote: ]
Subject: Re: Howto solve this in cvs ?
It is already done now with 2 vendor branches.. Moving the branch tag to
the corresponding vendor version does the job.. I tested commiting of
files on the two branches and it all
[ On Friday, October 12, 2001 at 09:51:54 (-0700), Gianni Mariani wrote: ]
Subject: RE: CVS - setup reserved checkout
There is a case where Greg would agree with you and that's in the case of
binary files or files that can't be merged automagically - like jpegs or
pngs.
yes, of course!
The entire loginfo file should look like the following:
# The loginfo file controls where cvs commit log information
# is sent. The first entry on a line is a regular expression which must
match
# the directory that the change is being made to, relative to the
# $CVSROOT. If a match is found,
* In message [EMAIL PROTECTED]
* On the subject of Re: [[EMAIL PROTECTED]: Re: rename in cvs]
* Sent on Fri, 12 Oct 2001 13:04:14 -0400 (EDT)
* Honorable [EMAIL PROTECTED] (Greg A. Woods) writes:
[ On , October 12, 2001 at 10:59:41 (-0400), Sam Steingold wrote: ]
Subject: Re: [[EMAIL
In article [EMAIL PROTECTED], Greg A. Woods wrote:
Even locking without lock contention won't solve all conflict
scenarios. Commit wars are possible with any change control process.
Even if you lock an entire repository, you can still get conflicts;
conflicts outside of the system.
Suppose I
In article [EMAIL PROTECTED], Bryon Lape wrote:
Kaz Kylheku wrote:
CVS doesn't require hand merging. When you perform a cvs update
operation, then new changes in the repository are automatically
incorporated into your working copy. Only when a conflict arises do
you have to do resolution by
On Fri, Oct 12, 2001 at 12:12:27PM -0400, Larry Jones wrote:
If you're using su to get to root, then CVS should be able to figure out
your real userid and you should be able to commit.
Only if you're using it locally. Client/server, it's the server
that does the getlogin(), and that has no
echo = new line
id = prints out user
echo %{sVv} = special cvs variable to print out version info
ar2kcm
- Original Message -
From: Postek, Jeffery
To: 'ar2kcm'
Sent: Friday, October 12, 2001 12:10 PM
Subject: RE: notify
I can't remember what the %s or %{sVv} string is for.
Please
Greg A. Woods writes:
Getlogin() is not always secure [*],
I'm not really sure what that's supposed to mean, but since we only use
it when the user is root (and hence can presumably spoof anything he or
she wants), I don't think it really matters.
and it's not really portable
despite
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 12, 2001 11:46 AM
To: [EMAIL PROTECTED]
Subject: RE: CVS - setup reserved checkout
[ On Friday, October 12, 2001 at 09:35:58 (-0500), Thornley,
David wrote: ]
Subject: RE: CVS -
I got there by going to http://sourceforge.net/ and typing rcvs in the
search field. That produced a table of about a dozen patches, one of
which had a suitable one-description. I clicked on that, then on the
download button.
--- Forwarded mail from [EMAIL PROTECTED]
Netscape tries and tries,
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
You need to ask yourself why your group is experiencing so many conflicts
while so many other groups (thousands?) are not.
Because there is no group, and there are no conflicts. This is just
another Chicken Little yelling that the sky is
One would hope that one's shop is not using the same branch for both
maintenance and new features. That kind of thing is best done on
separate branches (where the two schedules don't interfere with each
other). The bug fix is later merged into the new development when
it's appropriate to do so.
--- Forwarded mail from Greg Woods:
[ On Thursday, October 11, 2001 at 20:06:18 (-0700), Paul Sander wrote: ]
Subject: Re: cvs exit status
And your point is what? That it's okay to sometimes let nondeterministic
errors go undetected? Sorry, that's not good enough.
I think in real life the
--- Forwarded mail from [EMAIL PROTECTED]
[ On Friday, October 12, 2001 at 04:05:42 (GMT), Bryon Lape wrote: ]
Subject: Re: CVS - setup reserved checkout
The benefits add up to zero. Now, if it did method locking, that would be helpful,
protective AND productive. Without some sort of
--- Forwarded mail from [EMAIL PROTECTED]
[ On Thursday, October 11, 2001 at 23:08:38 (-0700), Paul Sander wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
I gain the requirement of having to type multiple cvs log or cvs rlog
commands, after figuring out every place a file has
--- Forwarded mail from [EMAIL PROTECTED]
[ On Thursday, October 11, 2001 at 23:12:44 (-0700), Paul Sander wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
--- Forwarded mail from Greg Woods:
Let me repeat: You DO NOT want or need to have cvs log BAR list
changes in the file
--- Forwarded mail from [EMAIL PROTECTED]
3 developers (A,B,C) need to fix file X.
A is making some major changes, adding lots of new functionality.
B and C need to make a minor tweak to the file.
In a CVS model:
B anc C can be done and outa there in minutes and essentially forget about
it.
I think the original poster was referring to access controls on the
primitive operations allowed on files by the version control system,
e.g. some users are not permitted to commit on certain branches,
others are not permitted to create tags, and so on.
--- Forwarded mail from [EMAIL PROTECTED]
Mark Lancisi writes:
I'd like to lock one of those projects. In other words, I'd like for
everyone, except maybe one or two users, to be read only users of one of
the projects. The other projects needs to remain read/write for all. It
looks like I can set this up at the repository level by
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 12, 2001 1:34 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: CVS - setup reserved checkout
One would hope that one's shop is not using the same branch for both
maintenance
[EMAIL PROTECTED] writes:
Is there a way to freeze the CVS tag? After we create a
CVS tag, we would
like to freeze it so that no one can change it and causes
problem, is this
possible?
You need to use a command in the CVSROOT/taginfo administrative file which
will exit with an
In article [EMAIL PROTECTED], Paul Sander wrote:
--- Forwarded mail from [EMAIL PROTECTED]
[ On Thursday, October 11, 2001 at 23:12:44 (-0700), Paul Sander wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
--- Forwarded mail from Greg Woods:
Let me repeat: You DO NOT want or need
Hi,
Is there a way to freeze the CVS tag? After we create a CVS tag, we would
like to freeze it so that no one can change it and causes problem, is this
possible?
Thanks in advance!
--
Terry Hung
___
Info-cvs mailing list
[EMAIL PROTECTED]
In article [EMAIL PROTECTED], Paul Sander wrote:
Under those conditions, almost any version control tool provides the
necessary merge tool.
Your inexperience is showing. There are version control tools in *broad*
use that have extremely support for branching and merging.
Exhibit A: Visual
Hello all, I was wondering if some of you nice people could give me some
feedback on an issue I've been wrestling with.
Besides the actual source code to a project, I also need the ability to
version design documentation ( and maybe other stuff, but this is my
immediate concern ). By design
Please drop me from the mailing list.
[ On Friday, October 12, 2001 at 14:36:01 (-0400), Larry Jones wrote: ]
Subject: Re: Why can't root check in files?
Greg A. Woods writes:
Getlogin() is not always secure [*],
I'm not really sure what that's supposed to mean, but since we only use
it when the user is root (and hence
[ On Friday, October 12, 2001 at 21:07:09 (GMT), Kaz Kylheku wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
Not really. CVS does not support renaming. In that sense, its version
management is incomplete. Let's not confuse incompleteness with
incorrectness. Deleting a file and
[ On , October 12, 2001 at 13:51:10 (-0400), Sam Steingold wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
Also, the manual does _not_ explain why cvs cannot do what is described
in http://www.cvshome.org/docs/manual/cvs_7.html#SEC72 with cvs mv
and
Has anyone written a utility to convert from true change to cvs ?
Get your FREE download of MSN Explorer at http://explorer.msn.com
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
--- Forwarded mail from [EMAIL PROTECTED]
In article [EMAIL PROTECTED], Paul Sander wrote:
--- Forwarded mail from [EMAIL PROTECTED]
[ On Thursday, October 11, 2001 at 23:12:44 (-0700), Paul Sander wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
--- Forwarded mail from Greg
In article [EMAIL PROTECTED], Paul Sander wrote:
It only looks broken when we call it renaming; calling it renaming doesn't
make it renaming.
Fine. CVS doesn't support renaming. We all know that. So it's incomplete.
Some would still claim that its lack of support for renaming means that
CVS
This should be a no-brainer, but I just can't get my CVS setup going.
I'm on Win2k, with Cygwin 1.3.2, CVS 1.11 (the cvs built into Cygwin).
I have a directory $HOME/java/sgs that I want to store into CVS.
I'm setting my CVSROOT to :local:/cygdrive/c/cvsroot.
I want to check out sgs into
[ On Saturday, October 13, 2001 at 01:23:14 (GMT), Kaz Kylheku wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
The problem is, I wouldn't hold my breath.
You'll certainly turn blue if you try.
CVS cannot easily ever support renaming to any extent that something
like BitKeeper or
--- Forwarded mail from [EMAIL PROTECTED]
CVS cannot easily ever support renaming to any extent that something
like BitKeeper or Perforce does, at least not without breaking backwards
compatabilty of the repository structure.
There's simply no place to put the extra meta data necessary except
[EMAIL PROTECTED] writes:
Is there a way to freeze the CVS tag? After we create a CVS tag, we would
like to freeze it so that no one can change it and causes problem, is this
possible?
No, but note that CVS won't move an existing tag unless you force it to
by using the -F flag -- simply
Wrong.
Kaz Kylheku wrote:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
You need to ask yourself why your group is experiencing so many conflicts
while so many other groups (thousands?) are not.
Because there is no group, and there are no conflicts. This is just
another
I simply clicked on the link you supplied. I even copied it to IE
just to make sure Nutscraper wasn't having a problem.
[EMAIL PROTECTED] wrote:
I was able to use Netscape get to the patches.
Exactly what are you doing?
Noel
Netscape tries and tries, but nothing is ever returned by this link.
I'm thinking that what I do works to not allow tag changes:
First, I define a 'cvsadmin' group.
Second, I place this line in $CVSROOT/CVSROOT/taginfo:
ALL $CVSROOT/CVSROOT/tagrules.sh
Third, I place tagrules.sh in my $CVSROOT/CVSROOT/checkoutlist
Fourth, my tagrules.sh looks like this:
[ On Friday, October 12, 2001 at 20:34:48 (-0700), Paul Sander wrote: ]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
They can be stored in newphrases inside the RCS files, without breaking
compatibility. It's still the wrong way to do it, but it's an improvement
over the status quo.
Hi,
Thanks for all the suggestions! Since I do not want the users to touch
an existing tag at all, I will add code in tagrules.sh to reject any
tagging request (tag, delete, etc) that involves an existing tag. My
version or David's tagrules.sh will be:
tag=$1 [tag]
op=$2
84 matches
Mail list logo
