From: "Tommy M. McGuire" <mcguire@crsr.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: "git cvsimport"
Date: Wed, 8 Jun 2005 00:32:40 -0500 [thread overview]
Message-ID: <20050608053240.GA28007@immutable.crsr.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0506071556000.2286@ppc970.osdl.org>
On Tue, Jun 07, 2005 at 04:03:53PM -0700, Linus Torvalds wrote:
>
> Ok,
> here's something for testers and/or documentation people: I wrapped a
> little script around cvs2git (which I imported from the git tools thing),
> and now you can do
>
> git cvsimport <cvsroot> <modulename>
>
> and it might all "just work".
>
> Right now the little sript is actually being anal and checking that
> CVSROOT is a directory, even though I think it all _should_ work even if
> CVSROOT is remote too. But I don't have any remote things to test, and for
> all I know maybe performance is horrible, so for now it artificially
> limits it to locally accessible CVS repos.
>
> I'd love it if somebody tested the remote case (and, if it works, sends me
> a patch that just removes the anal tests in git-cvsimport-script), and
> maybe even updated the information a bit more.. As it is, that
> Documentation/cvs-migration.txt file is a bit on the light side.
>
> Finally, I don't know what to do about cvsps options. It seems that the
> default time-fuzz is a bit too long for some projects, so at least that
> one should be overridable. So my silly script is not exactly wonderful,
> but I think it's more approachable than people doing the magic by hand
> (and forgetting to set TZ to UTC and the "-A" flag etc etc).
>
> Linus
It seems to work for me. I'm still sanity checking the results.
Performance is indeed horrible for the remote case. I don't know how
horrible it would be for someone in a sane environment, since I'm behind
one of SBC's DSL gateways, which thinks (emphasis on "thinks") it is a
nameserver.
The script produced by cvs2git checks out every revision of every file,
right? Would "cvsps -g -p<dir>" improve cvs2git? I don't think it
would help performance (it checks out the files to generate the patchset
diffs (?)), but making the ugly someone else's problem is always good.
Also, what about -x, to force cvsps to regenerate it's cached idea of
the repository's patchsets?
cvsps seems a little weak on the whole error message idea (misspelling
cvsroot leads to complaints about CVS versions).
--
Tommy McGuire
next prev parent reply other threads:[~2005-06-08 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 23:03 "git cvsimport" Linus Torvalds
2005-06-08 5:32 ` Tommy M. McGuire [this message]
2005-06-10 6:22 ` [PATCH] " Tommy M. McGuire
2005-06-10 6:27 ` [PATCH] git cvsimport sanity checking Tommy M. McGuire
2005-06-10 6:33 ` [PATCH] cvs-migration.txt Tommy M. McGuire
2005-06-10 6:38 ` [PATCH] git cvsimport fuzz argument Tommy M. McGuire
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=20050608053240.GA28007@immutable.crsr.net \
--to=mcguire@crsr.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).