All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add -k kill keyword expansion option to git-cvsimport
Date: Mon, 15 Aug 2005 19:52:42 +1200	[thread overview]
Message-ID: <46a038f90508150052308cf7a8@mail.gmail.com> (raw)
In-Reply-To: <7vvf273aqb.fsf@assigned-by-dhcp.cox.net>

On 8/15/05, Junio C Hamano <junkio@cox.net> 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

  reply	other threads:[~2005-08-15  7:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  6:51 [PATCH] Add -k kill keyword expansion option to git-cvsimport Martin Langhoff
2005-08-15  6:56 ` Martin Langhoff
2005-08-15  7:12 ` Junio C Hamano
2005-08-15  7:37   ` Martin Langhoff
2005-08-15  7:44     ` Junio C Hamano
2005-08-15  7:52       ` Martin Langhoff [this message]
2005-08-15  8:18     ` Junio C Hamano
     [not found]       ` <46a038f905081501301bd9a801@mail.gmail.com>
2005-08-15  8:48         ` Junio C Hamano
2005-08-15  9:05           ` Martin Langhoff
2005-08-15 11:20             ` Martin Langhoff
2005-08-16  0:12               ` Junio C Hamano
2005-08-16 11:29                 ` Martin Langhoff
  -- strict thread matches above, loose matches on Subject: below --
2005-08-15  7:10 Martin Langhoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46a038f90508150052308cf7a8@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.