Re: [PATCH] Add -k kill keyword expansion option to git-cvsimport

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Add -k kill keyword expansion option to git-cvsimport

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:04

Martin Langhoff [off-list ref] writes:
I think -kv is just the wrong thing to do if you are migrating to git.
Anyway, this script has so far followed cvs's own default... which is
-kv, and I am generally unwilling to break backwards compatibility.
Isn't cvs default -kkv?

Re: [PATCH] Add -k kill keyword expansion option to git-cvsimport

From: Martin Langhoff <hidden>
Date: 2016-06-15 22:42:04

On 8/15/05, Junio C Hamano [off-list ref] wrote:
Isn't cvs default -kkv?
You're right, default is -kkv (expand keyword/value every time) and
not -kv (expand keyword/value only if previously unexpanded).

There's something else in the -kb / -ko distinction according to the
protocol description I linked before. Using -kb changes the way the
file is sent, and this may well break our protocol handling, which is
currently quite happy to deal with the file as a series of lines.

OTOH I am not sure if it breaks when dealing with true binary stuff
like images, compressed data, etc.

cheers,


martin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help