From: Matthias Urlichs <smurf@smurf.noris.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Sven Verdoolaege <skimo@liacs.nl>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-cvsimport-script: parse multidigit revisions
Date: Tue, 26 Jul 2005 01:42:57 +0200 [thread overview]
Message-ID: <20050725234257.GC5680@kiste.smurf.noris.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0507251544300.6074@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]
Hi,
Linus Torvalds:
> In particular, they always end up being imported as zero-sized empty
> files, and will be filled in only later if that file is ever touched
> again. In other words, the resulting git tree ends up being bogus.
>
That's a problem with the bkcvs tree. Remember tht Bitkeeper does
exactly the same thing -- the 1.0 version of *any* file is empty, and
content appears only in version 1.1.
Well, the bkcvs export preserved that ... "feature".
(Side question - why aren't you doing a direct bk2git import?)
> Argument "28213 has collisions" isn't numeric in addition (+) at /home/torvalds/bin/git-cvsimport-script line 600, <CVS> line 1.
That's an output from cvsps that is not handled yet.
If you really need it I'll have to investigate.
> Btw, looking at what the perl script _seems_ to do, it does seem to do
> insane things for the local CVS archive case. As far as I can tell from
> the spaghetti that is perl, it uses a CVS server to handle even the local
> file case, which just _can't_ be right.
Sure it is, because ...
> I realize you'd want to do that to
> avoid connecting millions of times, but maybe it's better to use something
> like cvsnup to download the whole thing, and then always use a local CVS
> archive?
... I don't have a sensible RCS library for perl (the code that I could
find is just a command line front-end). Fork+exec of some cvs checkout
command per file is slower than just running a persistent CVS server.
I've tried other ideas, but they run into problems because some
idiots^Wpeople occasionally tag only parts of a CVS tree, or they do it
at different times, and cvsps has to rearrange stuff in a way the CVS
utilities don't understand, so any higher-level access than "grab a
bunch of files by their revision number and stick them into a commit"
don't work in real life.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
Please try to limit the amount of "this room doesn't have any bazingas"
until you are told that those rooms are "punched out." Once punched out,
we have a right to complain about atrocities, missing bazingas, and such.
-- N. Meyrowitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-25 23:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 21:35 [PATCH] git-cvsimport-script: parse multidigit revisions Sven Verdoolaege
2005-07-13 1:18 ` Matthias Urlichs
2005-07-25 23:00 ` Linus Torvalds
2005-07-25 23:42 ` Matthias Urlichs [this message]
2005-07-26 3:07 ` Linus Torvalds
2005-07-26 3:43 ` Linus Torvalds
2005-07-26 16:50 ` Linus Torvalds
2005-07-26 17:41 ` Rene Scharfe
2005-07-26 21:46 ` David Mansfield
2005-07-26 22:01 ` Linus Torvalds
2005-07-26 4:22 ` Ryan Anderson
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=20050725234257.GC5680@kiste.smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=git@vger.kernel.org \
--cc=skimo@liacs.nl \
--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