From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: ELKS Git repository up on SourceForge + patches applied
Date: Mon, 06 Feb 2012 11:11:05 +0000 [thread overview]
Message-ID: <4F2FB549.2070709@cowlark.com> (raw)
In-Reply-To: <20120205215323.72acc514@zorapide>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Mario Frasca wrote:
> I know there is a way to export a complete CVS repository with history
> to git as I did so recently for an other project also on sourceforge
> (csvjdbc), I can't remember much more than it was an extension to git,
> but google for it and you will surely find it.
I imported a big CVS repo into hg a little while ago. I think it wins
the award for the earliest timestamp on Sourceforge:
http://tack.hg.sourceforge.net/hgweb/tack/tack/log/4bea19e501ed
I bring this up because the CVS repository had lots of subtle
corruptions inside and I had to do a fair bit of manual tweaking before
it would import. (IIRC some files had been moved to Attic but there were
still outstanding pointers to the old files elsewhere.) To do this I had
to copy the whole repo database locally, rather than doing the import
directly from the remote server.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-06 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 19:12 ELKS Git repository up on SourceForge + patches applied Jody
[not found] ` <CAMKR1ysAyZ7sDkmOBnDCcgs1rtLKQ_jnmRWJodAJg1Kp8cYebA@mail.gmail.com>
2012-02-05 19:22 ` Jody
2012-02-05 19:32 ` Kirn Gill
2012-02-05 20:53 ` Mario Frasca
2012-02-05 21:09 ` Kirn Gill
2012-02-06 11:11 ` David Given [this message]
2012-02-05 21:14 ` Harley Laue
2012-02-05 23:17 ` Jody
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=4F2FB549.2070709@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).