>For what it's worth, when I was playing around, importing the source from >FedoraHosted to >GitHub was exceedingly trivial. It took just minutes. > >IIRC, I refreshed my local repo, reset my remote origin URL in .git/config to >GitHub, and >did a push. > >Current commiters would need to do the same. Once the URL was updated >everything just >worked. Also, as a wonderful surprise, it kept 'git log' >information in tact. If your >GitHub EMail matches the one for prior commits, >everything syncs up.
I can confirm this, I copied the official FedoraHosted repo to my Github account while doing some initial work on a new profile project. In doing so, it picked up all the commit history, release, branches, tags, and contributors. You can tell who of the committers already has GitHub accounts by the contributor list. It was as simple as Shawn mentioned, I cloned from FH to local then pushed from local to a new repo @ Github. https://github.com/nzwulfin/scap-security-guide is the GitHub repo in question (very old, no warrantees) -Matt Matt Micene Solution Architect, Platforms RHCA #100-002-435 DLT Solutions _______________________________________________ scap-security-guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
