* David Mansfield <[EMAIL PROTECTED]> wrote: > Ingo Molnar wrote: > >* Ingo Molnar <[EMAIL PROTECTED]> wrote: > > > > > >>the patches contain all the existing metadata, dates, log messages and > >>revision history. (What i think is missing is the BK tree merge > >>information, but i'm not sure we want/need to convert them to GIT.) > > > > > >author names are abbreviated, e.g. 'viro' instead of > >[EMAIL PROTECTED], and no committer information is > >included (albeit commiter ought to be Linus in most cases). These are > >limitations of the BK->CVS gateway i think. > > > > Glad to hear cvsps made it through! I'm curious what the manual > fixups required were, except for the binary file issue (logo.gif).
--cvs-direct was needed to speed it up from 'several days to finish' to 'several hours to finish', but it crashed on a handful of patches [i used the latest devel snapshot so this isnt a complaint]. (one of the crashes was when generating 1860.patch.) Also, 'cvs rdiff' apparently emits an empty patch for diffs that remove a file that end without having a newline character - but this isnt cvsps's problem. (grep for +++ in the patchset to find those cases.) > As to the actual email addresses, for more recent patches, the > Signed-off should help. For earlier ones, isn't their some script > which 'knows' a bunch of canonical author->email mappings? (the > shortlog script or something)? yeah, that's not that much of a problem, most of the names are unique, and the rest can be fixed up too. > Is the full committer email address actually in the changeset in BK? > If so, given that we have the unique id (immutable I believe) of the > changset, could it be extracted directly from BK? i think it's included in BK. Ingo - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html