On 2/28/07, Andy Parkins <andyparkins@xxxxxxxxx> wrote:
The config option gitcvs.allbinary may be set to force all entries to get the -kb flag.
Hi Andy, I am a bit confused here... why would we want to do this? We don't want to support keyword expansion, and that happens at the server end anyway. CVS clients are pretty dumb and will just write out the file we give them. When we are going to diff, they send the file to the server, and the server runs the diff. Etc. No smarts at the client end that care about -k options. Or are you trying to control newline mangling on Windows/Mac clients? I'm not even sure where that mangling happens. If that's the case, a repo-wide toggle is useless, you really want the per-file-type rules you mention. dazed and confused... martin - 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