From: Tom Tromey <tromey@redhat.com>
To: Binutils Development <binutils@sourceware.org>
Cc: GDB Development <gdb@sourceware.org>
Subject: git conversion status
Date: Mon, 14 Oct 2013 17:01:00 -0000 [thread overview]
Message-ID: <871u3n3hxc.fsf@fleche.redhat.com> (raw)
I've uploaded a new trial version of src.git. In this version:
* I've done the conversion with all the email address updates
* I fixed the encoding problem that Andreas noted
* I've tested the commit scripts and believe they work reasonably well
Please give it a try. I plan to "go live" soon.
This week I am going to convert DJ's sync scripts to work with git; and
also post the gdbadmin patches for review.
After that I think the conversion is complete. My plan for the big
switch is here. Pardon the detail, but I think this process can also
use a review, in case I've forgotten a step.
**Note** that the CVS->git convert I am using is not incremental, so
commit access will be down during the conversion. Based on past
conversions I'd say this will be a good part of one working day.
* Disable all commits to src CVS and rsync it locally
This is needed in case someone modifies a file that will remain
writable in CVS after the conversion; I want to ensure we get a
sensible snapshot.
The downtime here will be minimal for projects other than
gdb+binutils.
* Undo most of the commit disabling, leaving just those to the relevant
directories in the src CVS repository.
* Do the conversion, using the scripts I've written:
https://github.com/tromey/gdb-git-migration
These are well debugged at this point.
* Commit the git-related gdb and binutils patches to this new
repository.
* Copy the converted repository back to sourceware.
At this point git is live.
* Check in the web page changes
* Check in the gdbadmin changes
* Email Jim Meyering and ask him to disable the gdb.git and binutils.git
mirroring
* Email Alan Modra and to switch his auto-commit script over
* Send out an announcement.
* Be around to fix bugs
Due to the final item I would like to do the conversion on a Monday, to
maximize the time I'll be available after the conversion. I suggest
next Monday, October 21.
Tom
next reply other threads:[~2013-10-14 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 17:01 Tom Tromey [this message]
2013-10-14 17:07 ` Fred Cooke
2013-10-14 17:45 ` Tom Tromey
2013-10-14 19:01 ` Jan-Benedict Glaw
2013-10-14 19:07 ` Jan Kratochvil
2013-10-14 20:02 ` Andreas Schwab
2013-10-14 20:08 ` Tom Tromey
2013-10-14 20:11 ` Fred Cooke
2013-10-14 23:08 ` Joseph S. Myers
2013-10-15 13:18 ` Tom Tromey
2013-10-15 13:25 ` Fred Cooke
2013-10-15 15:09 ` Joseph S. Myers
2013-10-15 22:35 ` Hans-Peter Nilsson
2013-10-15 2:12 ` Hans-Peter Nilsson
2013-10-15 7:21 ` Andreas Schwab
2013-10-15 8:03 ` Tim Sander
2013-10-15 16:57 ` Richard Sandiford
2013-10-15 17:52 ` Stan Shebs
2013-10-15 9:56 ` Joel Brobecker
2013-10-15 13:19 ` Tom Tromey
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=871u3n3hxc.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.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