From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add -k kill keyword expansion option to git-cvsimport
Date: Mon, 15 Aug 2005 01:48:06 -0700 [thread overview]
Message-ID: <7vr7cv1t89.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f905081501301bd9a801@mail.gmail.com> (Martin Langhoff's message of "Mon, 15 Aug 2005 20:30:01 +1200")
Martin Langhoff <martin.langhoff@gmail.com> writes:
> Do you want just -kv or you'd like to handle all the modes?
No, I do not.
I was just wondering if we are limiting options for people who
want to convert their own CVS repositories by always using
either -kkv or -ko and nothing else. Your simply saying "I do
not think so, -ko is what makes the most sense, and any other
option does not make any sense, but we used to do -kkv so let's
leave that as the default and have a -k option that does -ko" is
enough for me.
It is getting late for me so I'll merge it and push it out
tomorrow when I find time; it will be my day-job day.
next prev parent reply other threads:[~2005-08-15 8:48 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 [this message]
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=7vr7cv1t89.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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).