Brian Behlendorf <[EMAIL PROTECTED]> writes: > If that's correct, I don't have the first clue on how to fix it. =) > Sounds more like a bug in the CVS client than anything I can fix on the > server side; I don't know the cvs code well enough to be comfortable > trying to fix this (nor do I really have the desire to spend the time > diving into CVS source code, given it's not a fatal error). But if anyone > does track it down and it's something I can fix on the server, I'll be > happy to do so.
It's a client problem, yes. Given that it's not a real problem, I'm inclined to pretend it's not happening...
