Hi,
>If I have the
> time I will look into a way to make CVS 1.10 make the files in the
> "Base" folder write protected to prevent myself and other developers
> from inadvertently editing these files after double-clicking on the file
> in the search result list in Developer's Studio. That's the only change
> I need. I somebody knows how to do this or have already done so, please
> let the rest of us know.
For Developer Studio the problem is solved for you if you use CvsIn. It will
kindly warn you if you try to open the file which is in the "*/Cvs/Base/"
directory and tell you not to edit it. So it is not important that the file
is writable - you will get the message box each time you activate such file
in the DevStudio.
CvsIn is a free, open source Add-in for the DevStudio, look for it at:
www.cvsin.org
or
http://www.geocities.com/kaczoroj/CvsIn/
As a side note I will only mention that sometime next week there will be an
internal CvsIn Beta release (you would have to join the CvsIn mailing list
to get it) which is using the file's copy in the /Cvs/Base/ to call an
external diff. It works fast and it doesn't require the connection to the
server. It will also show YOUR changes YOU made to the file since you made
'cvs edit', which is also good. Funny is that I used to hate that copy in
the /Base/ directory, now I've found a usage for it :)
Personally I think I want Unedit to revert the file's changes. WinCvs and
CvsIn (well, cvs.exe in fact) gives an option to revert the changes or not
if the file has been modified. I would rather want some patch to allow me to
force the revert and not having to interact with CVS at that point. It
complicates the shelling of cvs.exe client if Unedit is interactive.
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
