RE: [Info-cvs] Strict Locking patches etc

[Noel L Yap]

I don't have the mapping of patch numbers to meanings (and I don't have much
time to go to SourceForge).

The patches you need are the ones dealing with "cvs edit" and "cvs ci".  Other
patches (eg using client names on the server) aren't necessary.  In fact, the
client names patch is deemed insecure -- I plan to remove it, but I haven't had
the chance.

RTM on "cvs edit" and "cvs watch" to learn about this type of "locking" and
notification.

Noel




address@hidden on 2000.09.20 01:14:51

To:   address@hidden
cc:   address@hidden
Subject:  RE: [Info-cvs] Strict Locking patches etc




Hi Noel,
I apologize for sending too many emails, This is my first time to download
patch from your rcvs project site. I wanted to ask you if you have the cvs
tree some where, so that I dont have to get multiple patches and I can only
get the specific version files rather than merging lot of them .

It would be good idea to put the diff b/w the released(1.10.8) version and
the new patch version for the various patches that you have up there on the
site.  So that novices like me dont bug you a lot.
This is just a suggestion. I dont know what methodology people follow for
various software patches.

Do I just need to get patch number below or do I need the ones with the
question marks as well

100321
100323
100324
100327
100328
100332
100586?
100588?
100595? 100596?

Is there a way to release a lock on a file without making any changes to it.

Again I thank you for all the support that you have provided me.

Regards,

-Adnan



-----Original Message-----
From: Noel L Yap [mailto:address@hidden
Sent: Monday, September 18, 2000 4:50 PM
To: address@hidden
Cc: address@hidden
Subject: RE: [Info-cvs] Strict Locking patches etc


The normal "cvs editors" command will work fine.

The patches can be downloaded from SourceForge (project RCVS).  They are
against
cvs-1.10.8.

cvs-1.10.8 does not incorporate the patches.

Also note that some of the patches extend the meaning of valid edits
(cvs-1.10.8
has edits per file per user, the patches has edits per file per location (ie
hostname/working directory) per user).

Noel




address@hidden on 2000.09.18 19:20:41

To:   address@hidden
cc:   address@hidden
Subject:  RE: [Info-cvs] Strict Locking patches etc




Hi Noel,

Thanks for the info. Is there a way to get the status back  on that
particular file whether it is locked or not. Where do I download the patches
from, if a  cvs release with patches is available that will be great. One of
my earlier questions does 1.10.8 incorporate the patches?

-Adnan

-----Original Message-----
From: Noel L Yap [mailto:address@hidden
Sent: Monday, September 18, 2000 3:00 PM
To: address@hidden
Cc: address@hidden
Subject: Re: [Info-cvs] Strict Locking patches etc






address@hidden on 2000.09.18 16:01:05
>I have been browsing the egroups message boards/rcvs @sourceforge.net.
>What I need to ask you is firstly I need  the patches for the strict
>locking, where can I download them from, I only see the patches for the
>patches for the/ which ones do I need. Also Is there a way with the "cvs
>edit" to know if the file is already locked by a user(or include a swtitch
>with cvs status to include this feature if not already there).
>I had been using the admin -l here but need to switch to either rcs
>(dont want to because of the features that cvs provides you with) or to
stay
>with cvs if there is some feature that can allow me to have a error free
>strict locking. Also is there some way to to remove the question which cvs
>asks if you try to use cvs admin -l on a file that is already locked by
>another user(Do you want to break the lock?) or have a status which can
tell
>me about the locks.
>
>I appreciate your help in this regards,

Take a look at the patches for "cvs edit -c", "cvs edit -f", and "cvs ci
-c".
They're not exactly what you're asking for, but they're close.  CVS has no
real
strict locking.  What these patches do is mimic locking (eg "cvs edit -c"
will
abort if there exists another edit on the file(s) and "cvs ci -c" will abort
if
the user doesn't have a valid edit on the file(s)).  "cvs edit -f" allows
users
to override an "edit -c" in their .cvsrc file.

The assumption that these patches make is that developers respect the
groups'
procedures.  If it's deemed that users should never "cvs edit -f" certain
files,
and you find that they do (and that it causes problems for others), they
need
some disciplining.

Noel



This communication is for informational purposes only.  It is not intended
as
an offer or solicitation for the purchase or sale of any financial
instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.

Hi Noel,
I apologize for sending too many emails, This is my first time to download patch from your rcvs project site. I wanted to ask you if you have the cvs tree some where, so that I dont have to get multiple patches and I can only get the specific version files rather than merging lot of them .

It would be good idea to put the diff b/w the released(1.10.8) version and the new patch version for the various patches that you have up there on the site.  So that novices like me dont bug you a lot.

This is just a suggestion. I dont know what methodology people follow for various software patches.

Do I just need to get patch number below or do I need the ones with the question marks as well
 
100321
100323
100324
100327
100328
100332
100586?
100588?
100595? 100596?

Is there a way to release a lock on a file without making any changes to it.
Again I thank you for all the support that you have provided me.

Regards,

-Adnan

-----Original Message-----
From: Noel L Yap [mailto:address@hidden]
Sent: Monday, September 18, 2000 4:50 PM
To: address@hidden
Cc: address@hidden
Subject: RE: [Info-cvs] Strict Locking patches etc

The normal "cvs editors" command will work fine.

The patches can be downloaded from SourceForge (project RCVS).  They are against
cvs-1.10.8.

cvs-1.10.8 does not incorporate the patches.

Also note that some of the patches extend the meaning of valid edits (cvs-1.10.8
has edits per file per user, the patches has edits per file per location (ie
hostname/working directory) per user).

Noel

address@hidden on 2000.09.18 19:20:41

To:   address@hidden
cc:   address@hidden
Subject:  RE: [Info-cvs] Strict Locking patches etc

Hi Noel,

Thanks for the info. Is there a way to get the status back  on that
particular file whether it is locked or not. Where do I download the patches
from, if a  cvs release with patches is available that will be great. One of
my earlier questions does 1.10.8 incorporate the patches?

-Adnan

-----Original Message-----
From: Noel L Yap [mailto:address@hidden]
Sent: Monday, September 18, 2000 3:00 PM
To: address@hidden
Cc: address@hidden
Subject: Re: [Info-cvs] Strict Locking patches etc

address@hidden on 2000.09.18 16:01:05
>I have been browsing the egroups message boards/rcvs @sourceforge.net.
>What I need to ask you is firstly I need  the patches for the strict
>locking, where can I download them from, I only see the patches for the
>patches for the/ which ones do I need. Also Is there a way with the "cvs
>edit" to know if the file is already locked by a user(or include a swtitch
>with cvs status to include this feature if not already there).
>I had been using the admin -l here but need to switch to either rcs
>(dont want to because of the features that cvs provides you with) or to
stay
>with cvs if there is some feature that can allow me to have a error free
>strict locking. Also is there some way to to remove the question which cvs
>asks if you try to use cvs admin -l on a file that is already locked by
>another user(Do you want to break the lock?) or have a status which can
tell
>me about the locks.
>
>I appreciate your help in this regards,

Take a look at the patches for "cvs edit -c", "cvs edit -f", and "cvs ci
-c".
They're not exactly what you're asking for, but they're close.  CVS has no
real
strict locking.  What these patches do is mimic locking (eg "cvs edit -c"
will
abort if there exists another edit on the file(s) and "cvs ci -c" will abort
if
the user doesn't have a valid edit on the file(s)).  "cvs edit -f" allows
users
to override an "edit -c" in their .cvsrc file.

The assumption that these patches make is that developers respect the
groups'
procedures.  If it's deemed that users should never "cvs edit -f" certain
files,
and you find that they do (and that it causes problems for others), they
need
some disciplining.

Noel

This communication is for informational purposes only.  It is not intended
as
an offer or solicitation for the purchase or sale of any financial
instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.