Re: Migration from CVS to GIT
Martin Storsjö <[email protected]> Tue, 24 Jan 2012 11:27:44 +0200 (EET)
| Newsgroups | gmane.comp.encryption.nettle.bugs,gmane.network.lsh.bugs |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-977760248-1327397265=:27129 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hi, On Tue, 24 Jan 2012, Niels M=F6ller wrote: > I'm finally looking into conversion of the lsh repository from CVS to > GIT, and this naturally also includes nettle. This is great news! > If this first steps works out ok, step two is to do a some cleanups > (switching to utf-8 for the files, deleting old $Id$ tags, etc). And th= en > step three is to extract the nettle subdirectory as an independent > project and repository, using git subtree of git filter-branch or so > (I'm not sure what's the best tool for that job). Other sub-projects, > e.g., the argp implementation, can be split out later, if desired. I'd hope for a round of filter-branch to rewrite author names in git to=20 the original author of patches. I haven't done it myself, but I've seen i= t=20 done on other projects. One can do some kind of more or less heuristic=20 shell script that e.g. greps the commit message for known strings (either= =20 known contributors or strings like "From:" or "contributed by") and based= =20 on these override the author name. If you don't feel up to doing this yourself, I can try to give it a go. // Martin --8323329-977760248-1327397265=:27129 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nettle-bugs mailing list nettle-bugs-UqbJ+GOpo48MZebb/[email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs --8323329-977760248-1327397265=:27129--