[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MIT-Scheme-devel] git?
From: |
Matt Birkholz |
Subject: |
Re: [MIT-Scheme-devel] git? |
Date: |
Wed, 29 Apr 2009 14:08:59 -0700 |
> From: address@hidden (Matt Birkholz)
> Date: Tue, 28 Apr 2009 10:22:05 -0700
>
> [...]
> git-cvsimport finished without error after approx. 2 hours (while The
> East Coast slept).
The latest git-cvsimport (cut off at RELEASE_7_3_0) finished in 2.75
hours.
> Does anyone object to me pushing this to git.sv.gnu.org:/srv/git/
> mit-scheme.git?
>
> I am working on a cron job so that it will track CVS daily.
I do not know how easy it is to nuke a botched repo. on
git.sv.gnu.org, so I am just making this available here:
git://birkholz.chandler.az.us/mit-scheme.git
DO NOT USE except for evaluation purposes. I may want to toss it and
start again, depending on your feedback. The reason: I flattened the
directory structure in CVS somewhat.
Specifically, I did not import mit-scheme/v8 at all; it looks like it
belongs on a branch. And I pushed mit-scheme/etc down into
mit-scheme/v7 so that the top-level working directory contains:
dist/ <- cvsroot/mit-scheme/v7/dist
doc/ <- cvsroot/mit-scheme/v7/doc
etc/ <- cvsroot/mit-scheme/etc
src/ <- cvsroot/mit-scheme/v7/src
What do y'all think? Can v8 go on a branch?
> [...] I can checkout RELEASE_7_3_0, but not RELEASE_7_1_0 or
> earlier. I get an error like this:
>
> cvs [checkout aborted]: invalid change text in
> /cvsroot/mit-scheme/mit-scheme/v7/src/microcode/comlin.c,v
>
> I will re-run the initial git-cvsimport with -r RELEASE_7_3_0 tonight.
> If anyone wants to git anything older, we should talk.
I was able to get ALL of the revisions of src/runtime/hash.scm by
"repairing" its ,v file, but it took a bit of fiddling. Only 2 of the
~180 files in src/runtime/ were broken, so repairing all of them may
not be infeasible. If we do that, we will probably need to toss the
repo. I just made (unless cvsps and git-cvsimport can prepend the
newly available history).
Anyway, I will be using a clone of this repo. to track CVS and manage
my local FFI and Gtk patchsets. It is easy enough(?) to pull patches
out and apply them to CVS.
It's funny: the brokenness is not random. I have to wonder if these
revisions were EVER accessible -- ever accessed!
- [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/25
- Re: [MIT-Scheme-devel] git?, Taylor R Campbell, 2009/04/25
- Re: [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/25
- Re: [MIT-Scheme-devel] git?, Chris Hanson, 2009/04/26
- Re: [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/26
- Message not available
- Re: [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/27
- Re: [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/27
- Re: [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/28
- Re: [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/28
- Re: [MIT-Scheme-devel] git?,
Matt Birkholz <=
- Re: [MIT-Scheme-devel] git?, Matt Birkholz, 2009/04/29