git.vger.kernel.org archive mirror
 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 23:20:16 +1200	[thread overview]
Message-ID: <46a038f9050815042036616b08@mail.gmail.com> (raw)
In-Reply-To: <46a038f9050815020511574e3d@mail.gmail.com>

On 8/15/05, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> I think the other modes are relevant in different scenarios. -kv is
> only meaningful as file mode over the life of the file in the repo.
> -kk is only meaningful when calling cvs update with -j -j parameters
> or cvs diff, and is effectively a synonim of -ko.
> 
> In the position we are, getting file/revisions out of a repo, there
> are 2 possible files we can get: the one that you'll get with -kkv and
> the one you'll get with -ko/-kb. -kb/-ko should give us exactly the
> same file, modulo bugs.

After a few more trial runs, it ends up being that -kb and -ko drop
the ball in some instances, and the most reliable flag to send is -kk.
Don't ask me how or why.

So this patch is obsolete too. 



martin

  reply	other threads:[~2005-08-15 11:20 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
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 [this message]
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=46a038f9050815042036616b08@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).