From: Shawn Pearce <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, monotone-devel@nongnu.org, dev@rapidsvn.tigris.org
Subject: Re: cvs import
Date: Thu, 14 Sep 2006 12:18:09 -0400 [thread overview]
Message-ID: <20060914161809.GA9885@spearce.org> (raw)
In-Reply-To: <eebuih$u32$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> wrote:
> Shawn Pearce wrote:
>
> > Originally I wanted Jon Smirl to modify the cvs2svn (...)
>
> By the way, will cvs2git (modified cvs2svn) and git-fast-import publicly
> available?
Yes. I want to submit git-fast-import to the main Git project and
ask Junio to bring it in.
However right now I feel like the code isn't up-to-snuff and won't
pass peer review on the Git mailing list. So I wanted to spend a
little bit of time cleaning it up before asking Junio to carry it
in the main distribution. My pack mmap window code is actually
part of that cleanup.
I think the goal of this thread is to try and merge the ideas
behind Jon's modified cvs2svn into the core cvs2svn, possibly
causing cvs2svn to be renamed to cvs2notcvs (or some such) and
having a slightly more modular output format so Git, Monotone and
Subversion can all benefit from the difficult-to-do-right changeset
generation logic.
--
Shawn.
next prev parent reply other threads:[~2006-09-14 16:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45084400.1090906@bluegap.ch>
2006-09-13 19:01 ` cvs import Jon Smirl
2006-09-13 20:41 ` Martin Langhoff
2006-09-13 21:04 ` Markus Schiltknecht
2006-09-13 21:15 ` Oswald Buddenhagen
2006-09-13 21:16 ` Martin Langhoff
2006-09-14 4:17 ` Michael Haggerty
2006-09-14 4:34 ` Jon Smirl
2006-09-14 5:02 ` Michael Haggerty
2006-09-14 5:21 ` Martin Langhoff
2006-09-14 5:35 ` Michael Haggerty
2006-09-14 5:30 ` Jon Smirl
2006-09-14 4:40 ` Martin Langhoff
2006-09-13 21:05 ` Markus Schiltknecht
2006-09-13 21:38 ` Jon Smirl
2006-09-14 5:36 ` Michael Haggerty
2006-09-14 15:50 ` Shawn Pearce
2006-09-14 16:04 ` Jakub Narebski
2006-09-14 16:18 ` Shawn Pearce [this message]
2006-09-14 16:27 ` Jon Smirl
2006-09-14 17:01 ` Michael Haggerty
2006-09-14 17:08 ` Jakub Narebski
2006-09-14 17:17 ` Jon Smirl
2006-09-15 7:37 ` Markus Schiltknecht
2006-09-16 3:39 ` Shawn Pearce
2006-09-16 6:04 ` Oswald Buddenhagen
2006-09-16 6:21 ` Nathaniel Smith
2006-09-13 22:52 ` Nathaniel Smith
2006-09-13 23:21 ` Daniel Carosone
2006-09-13 23:52 ` [Monotone-devel] " Daniel Carosone
2006-09-13 23:42 ` Keith Packard
2006-09-14 0:32 ` Nathaniel Smith
2006-09-14 0:57 ` [Monotone-devel] " Jon Smirl
2006-09-14 1:53 ` Daniel Carosone
2006-09-14 2:30 ` [Monotone-devel] " Shawn Pearce
2006-09-14 3:19 ` Daniel Carosone
2006-09-14 21:57 ` [Monotone-devel] " Petr Baudis
2006-09-14 22:04 ` Shawn Pearce
2006-09-14 2:35 ` Shawn Pearce
2009-02-16 9:17 CVS import Ferry Huberts (Pelagic)
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=20060914161809.GA9885@spearce.org \
--to=spearce@spearce.org \
--cc=dev@rapidsvn.tigris.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=monotone-devel@nongnu.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).