This is the mail archive of the
mailing list for the newlib project.
Re: newlib git?
- From: Tom Tromey <tromey at redhat dot com>
- To: Joel Sherrill <joel dot sherrill at OARcorp dot com>
- Cc: Jeff Johnston <jjohnstn at redhat dot com>, newlib at sourceware dot org, Corinna Vinschen <vinschen at redhat dot com>
- Date: Thu, 21 Nov 2013 11:00:22 -0700
- Subject: Re: newlib git?
- Authentication-results: sourceware.org; auth=none
- References: <528B9DB2 dot 6070207 at oarcorp dot com> <e5a3331fce124b75a3d3936ef235595e at DB3PR04MB203 dot eurprd04 dot prod dot outlook dot com> <20131119231245 dot GA512 at ednor dot casa dot cgf dot cx> <528BF679 dot 6070808 at oarcorp dot com> <625946994 dot 29075535 dot 1384978397722 dot JavaMail dot root at redhat dot com> <20131121151031 dot GA1761 at ednor dot casa dot cgf dot cx>
cgf> I'm sure that Tom will be willing to do some handholding but he probably
cgf> doesn't want to be "Mr. Git" for every project on sourceware.
The good news is that all the heavy lifting is done and, for the most
The binutils-gdb conversion was very hairy because it involved stitching
together ancient (pre-devo) gdb release tarballs, a pre-"src" drop of
part of devo, and then of course the "src" history.
If you want to do this, all the scripts are available, but you'll still
need to do some reasonably serious testing yourself:
If you don't mind a "simple" conversion, you can clone the above and
follow the directions in README.md, skipping the "old releases" and
"devo" and "graft-and-filter" steps.
The only real gotcha is that the user map I used is tailored to
binutils-gdb. You may have users not appearing in there. So, you will
need to update it to suit.