Paolo Bonzini <bonzini@xxxxxxx> writes: > Junio C Hamano wrote: >> Paolo Bonzini <bonzini@xxxxxxx> writes: >> >>> git-cvsserver does not support changes of type T (file type change, >>> e.g. symlink->real file). This patch treats them the same as changes >>> of type M. >> >> Hmm. >> >> Do cvs clients even know how to handle symlinks, or will this patch just >> start sending the readlink(2) result as if it is just a regular file >> contents? > > It was before too. The problem arises if one found the problem, > deleted the symlink, added the regular file -- and now cvsserver stops > working at all. :-( I fully agree that "stops working at all" was baaaaad, and your patch may be an improvement. What I am questioning is what the code should do (IOW, what would be good for cvs clients to see). Should it send a symlink as a regular file, or simply just omit it? If the answer is "the former", then we do not have to worry about it any further after applying your patch. Otherwise we still have to do something _else_ after applying your patch. I did not know which way we would want to proceed, and I still don't. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html