| commit | 8538e876b191901b7d37ec34a83287e51df91816 | |
| author | Andy Parkins <andyparkins@gmail.com> | |
| Tue, 27 Feb 2007 13:46:55 +0000 (27 13:46 +0000) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Wed, 28 Feb 2007 00:01:58 +0000 (27 16:01 -0800) | ||
| tree | 2a1943c3ff1326dd46545ce5090d1f4054ce8fb3 | treesnapshot (tar.gz zip) |
| parent | 1872adabccdd904f31f16276b147c63fa03079d4 | commitdiff |
cvsserver: Make always-binary mode a config file option
The config option gitcvs.allbinary may be set to force all entries to
get the -kb flag.
In the future the gitattributes system will probably be a more
appropriate way of doing this, but that will easily slot in as the
entries lines sent to the CVS client now have their kopts set via the
function kopts_from_path().
In the interim it might be better to not just have a all-or-nothing
approach, but rather detect based on file extension (or file contents?).
That would slot in easily here as well. However, I personally prefer
everything to be binary-safe, so I just switch the switch.
Signed-off-by: Andy Parkins <andyparkins@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
The config option gitcvs.allbinary may be set to force all entries to
get the -kb flag.
In the future the gitattributes system will probably be a more
appropriate way of doing this, but that will easily slot in as the
entries lines sent to the CVS client now have their kopts set via the
function kopts_from_path().
In the interim it might be better to not just have a all-or-nothing
approach, but rather detect based on file extension (or file contents?).
That would slot in easily here as well. However, I personally prefer
everything to be binary-safe, so I just switch the switch.
Signed-off-by: Andy Parkins <andyparkins@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| git-cvsserver.perl | diffblobblamehistory |