From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cvsimport: skip commits that are too recent
Date: Mon, 8 Jan 2007 16:18:59 +1300 [thread overview]
Message-ID: <46a038f90701071918y4a8078can90ae69dd1d9f9ffd@mail.gmail.com> (raw)
In-Reply-To: <7vd55qz2d1.fsf@assigned-by-dhcp.cox.net>
On 1/8/07, Junio C Hamano <junkio@cox.net> wrote:
> Well I meant to say that my conclusion is that that flag is not
> needed in practice.
you are getting soft in your old age, man :-)
More seriously, as soon as I sent the patch I thought of the use case
you describe. Not everyone is as patient as you are, and someone may
have things scripted. If the cvs repo is local/fast and under your
control, it doesn't make sense to be _so_ conservative.
Also -- by having the flag we get an excuse to mention it in the doco.
m
next prev parent reply other threads:[~2007-01-08 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 1:11 [PATCH] cvsimport: skip commits that are too recent Martin Langhoff
2007-01-08 1:59 ` Junio C Hamano
2007-01-08 2:13 ` Martin Langhoff
2007-01-08 2:19 ` Junio C Hamano
2007-01-08 3:18 ` Martin Langhoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-08 6:43 Martin Langhoff
2007-01-08 7:17 ` Martin Langhoff
2007-01-08 8:24 ` Martin Langhoff
2007-01-11 8:22 ` Robin Rosenberg
2007-01-11 20:18 ` 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=46a038f90701071918y4a8078can90ae69dd1d9f9ffd@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).