Re: Suppressing log suppression (down with the -l switch)
"Paul Edwards" <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.bugs |
|---|---|
| Organization | BigPond Internet Services (http://www.bigpond.net.au) |
| Message-ID | <[email protected]> |
"Derek Robert Price" <[email protected]> wrote in message news:[email protected]... > Done. Any opinions on whether I should back-port that to 1.11.x? I > think I could look at this as a security fix and I don't think the > change was invasive enough to affect stability, but I'm not too worried > about it. Yes, I think 1.11.x should have integrity if reasonably possible. Suitable for use by a company that can "absolutely guarantee" that they know exactly what happened to their source code at every step of the way, not subject to the whim of cowboys. Unless there is already a plethora of integrity holes in CVS so there's really no point? But I'm not aware of any myself (not that I've looked). I can remember a very long time ago I used to have to disable the admin command to stop people from being able to do things like remove revisions. I don't know if use of that command is now able to be restricted. Where I'm working at the moment, I'm a programmer, not CM, so I don't have to worry about security risks, the entire repository can be wiped out by my colleagues any time they want. I'm nominally supposed to be using PVCS. Basically I use CVS as a precursor to using PVCS, and no-one has sacked me for doing so. Yet. :-) BFN. Paul.