From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: What's in git.git (part #2)
Date: Thu, 1 Jun 2006 15:51:54 -0700 [thread overview]
Message-ID: <20060601225152.GG32457@h4x0r5.com> (raw)
In-Reply-To: <7v64jli66m.fsf@assigned-by-dhcp.cox.net>
On Thu, Jun 01, 2006 at 02:19:45AM -0700, Junio C Hamano wrote:
> Things that we might want to have in 1.4.0 but not even in "next"
> yet include:
>
> - p4 importer (Sean Estabrooks) -- are people interested?
I think adding more importers is a good thing. There's no sense in
having people reinvent the wheel.
Which reminds me, I need to polish and send off my BitKeeper importer.
(It's slow and dumb, but works.)
next prev parent reply other threads:[~2006-06-01 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 9:19 What's in git.git (part #2) Junio C Hamano
2006-06-01 9:23 ` Junio C Hamano
2006-06-01 9:31 ` Jakub Narebski
[not found] ` <20060601072637.9920c8c5.seanlkml@sympatico.ca>
2006-06-01 11:26 ` Sean
2006-06-01 22:51 ` Ryan Anderson [this message]
2006-06-02 2:35 ` Shawn Pearce
2006-06-02 6:40 ` Junio C Hamano
2006-06-06 5:39 ` Shawn Pearce
2006-06-06 6:16 ` Junio C Hamano
2006-06-06 8:19 ` Johannes Schindelin
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=20060601225152.GG32457@h4x0r5.com \
--to=ryan@michonline.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).