From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: fastimport pull request
Date: Sun, 24 Jun 2007 18:56:43 -0400 [thread overview]
Message-ID: <20070624225643.GL17393@spearce.org> (raw)
In-Reply-To: <7vr6o1ouv9.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <gitster@pobox.com> wrote:
> I had an impression from reading #git log and mailing list
> traffic, that you guys were afraid that the development history,
> and especially the commit log messages on this branch, were, eh,
> less than optimal. So I got curious and took a look --- it does
> not look too bad. It is a nontrivial amount of code (1.5k lines
> of Python) and is understandable to have meaningful history
> behind it.
That was true of the first version of the branch offered up by Simon.
After my initial reply Simon cleaned up the history and made many
of the messages more meaningful, and added SBO lines to them.
So the history you saw when you pulled was much improved over the
original version we were discussing on the list.
--
Shawn.
prev parent reply other threads:[~2007-06-24 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070622232458.GK17393@spearce.org>
2007-06-24 22:22 ` fastimport pull request Junio C Hamano
2007-06-24 22:56 ` Shawn O. Pearce [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=20070624225643.GL17393@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.