Dear Noel,
> The interface to CVS with my patch is: "cvs edit" will save a backup
using the
> standard naming conventions for backups. "cvs unedit" will not modify the
> existing file. This is an extremely simple interface.
Hm... If unedit will not modify the existing file than what is the use of
backup?
The interface is "extremely simple" in the worst meaning of "extreme".
> If flags were added, there'd be a few unlesses for the "cvs unedit"
interface.
> It'd be more complicated.
Yep, but many functionality is already there, it might just need "-f" to
force the revert from backup.
It doesn't matter if it's complicated, it must be USEFUL first of all.
> If so, those side effects are highly documented and consistent (ie they're
not
> side effects).
Since when "documented side effects" stop to be ones? They're still side
effects.
> No they can't. What part of "\"cvs edit\" saves a copy of the file the
way it
> was at the time of \"cvs edit\"" don't you understand? Or, can you
explain how
> you'd go about using timestamps to figure out if something has happened to
the
> backup?
OK, forget about the timestamps. Just:
1. make it readonly.
2. rename it a bit to avoid the cinfusion, especially change the extension
so the grep tools will no more pick it up. THe way to rename with the
revision number appended to the name sounds as a perfect solution.
This two steps are simple, consistent and USEFUL, they don't breake current
behaviour and they solve most problems with the backup copy.
> I haven't been able to figure out a way to see if there is a connection or
not.
> Perhaps someone can help out here? I've seen other occassions to know the
> connectability status.
You can just attempt normal connection and wait to see if it will fail.
> From what I've seen in the past, you seem to have been hacking WinCVS. If
this
> is true, you should be able to easily (since the interface is so simple)
hack
> WinCVS to do most of what you want.
Sure I can. But I would not for example attempt to put the code with
hardcoded setting to access my company repository into the public. I patch
to my needs but FIRST of all I will think how common problem and how generic
solution is.
> If you feel otherwise, don't use my patch (or patch it up some more).
> Seriously, though, none of the others have jumped in 'cos they don't use
"cvs
> edit" and "cvs unedit". I think I'm the only one who does who also wants
to
> maintain the CVS philosophy of keeping the tool simple.
Hm... the others did jumped, Most if not all WinCvs users are using
edit/unedit all the time since that is how the tool works best. They are
complaining about your patch, "hear the voices" and maybe revise your patch
a little bit? Onestly I was hoping that one day we would support RCVS at
least to get 'csv edit -c' functionality and kick off the admin locks. Try
to keep RCVS more/less consistent with the CVS...?
Cheers,
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.
