From: Junio C Hamano <junkio@cox.net>
To: "Martin Langhoff" <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cvsimport: complete the cvsps run before starting the import - BAD
Date: Wed, 07 Jun 2006 18:16:28 -0700 [thread overview]
Message-ID: <7vk67se9ar.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f90606071706w46567f6j4f4addae5c877537@mail.gmail.com> (Martin Langhoff's message of "Thu, 8 Jun 2006 12:06:23 +1200")
"Martin Langhoff" <martin.langhoff@gmail.com> writes:
> As far as I can see, you had the good sense of not applying this one.
> It is bad, and should be dropped.
Actually it wasn't sense but distraction. I got sidetracked
while looking at the patch.
prev parent reply other threads:[~2006-06-08 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 0:06 [PATCH] cvsimport: complete the cvsps run before starting the import - BAD Martin Langhoff
2006-06-08 1:16 ` Junio C Hamano [this message]
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=7vk67se9ar.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