> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Subject: Re: cvs ci, cvs upd: Hard linkage problem
>
>
> Leeuw, Guus writes:
> >
> > Larry, do we want this to be fixed (code stems from March
> 1998 according to
> > ChangeLogs)?
> > Will it have chance to become an official bug fix? (No need
> to waste time on
> > something
> > that will never propagate anyways...)
>
> As I say almost weekly, the PreservePermissions code is notoriously
> buggy and (in its current state) should not be used -- I've
> disabled it
> by default in the current development version. That said,
That was one of the options I would have gone for as well :-)))
> I'm not sure
> how much demand there is for it. Certainly, it's something
> that new CVS
> users seem to think they want, but when they try to use it and CVS
> crashes, they usually get told that they shouldn't be trying to store
> links in the repository anyway, and they accept that and go on without
> it. I haven't heard anyone complain that they absolutely have to have
> it.
>
> So, while I'm willing to accept patches, I'm not going to encourage
> them. And I will insist that any patches include test cases in
> sanity.sh to verify that the functionality works and continues to work
> in the future. (Please note that writing sanity tests that crash the
> current PreservePermissions code would be a valuable exercise
> in and of
> itself, assuming that someone does eventually want to fix it.)
All fair enough. Now, I was not using this because I needed to, but
because CVS out of the box comes with enabled. I suppose quite a
lot will/have stumble(d) over it.
I'll see what I can come up with in my sparetime.
Cheers,
Guus
