From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: fastimport pull request
Date: Sun, 24 Jun 2007 15:22:50 -0700 [thread overview]
Message-ID: <7vr6o1ouv9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20070622232458.GK17393@spearce.org
"Shawn O. Pearce" <spearce@spearce.org> writes:
> The following changes since commit 45fd8bd32dd68ce6b14a406d0abbd6f56490131c:
> Ismail Dönmez (1):
> Change default man page path to /usr/share/man
>
> are available in the git repository at:
>
> repo.or.cz:/srv/git/git/fastimport.git master
>
> and are intended for your master branch, aka the 1.5.3 series.
>
> Shawn O. Pearce (2):
> Avoid src:dst syntax as default bash completion for git push
> Import branch 'git-p4' of git://repo.or.cz/fast-export
>
> Yes, that's right, I pulled in Simon's git-p4 work. :-)
>
> Benjamin Sergeant (1): ...
> Han-Wen Nienhuys (30): ...
> Kevin Green (1): ...
> Marius Storm-Olsen (7): ...
> Simon Hausmann (222): ...
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.
Pulled, and pushed out.
next parent reply other threads:[~2007-06-24 22:22 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 ` Junio C Hamano [this message]
2007-06-24 22:56 ` fastimport pull request Shawn O. Pearce
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=7vr6o1ouv9.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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).