Even if you don’t bring in your full history when you move to an eclipse github repository, it is well worth making sure that the first commit to the new repo is exactly the same as the final commit in the old one.
If you do this, then you can use git replace to graft the old history onto the new history any time that you want the full history. You need access to both repos, and it’s a good idea to add instructions on how to do the replacement, but it’s quite a powerful technique. See https://git-scm.com/blog/2010/03/17/replace.html for a complete example. Take care, Mark………. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 03 October 2017 17:55 To: Kevin Herron; Discussions for new Eclipse projects Subject: Re: [incubation] How do we move github repos from our organisation tothe Eclipse organisation? OK, maybe it was easier for us because and really only a short history of several months. I hope didn't bring more confusion. I just wanted to point out that Eclipse, ad Wayne especially, has been always open to discussion over “have tos” and were very helpful. At worst, you’ll get through explanation for “have to” if you ask, as Wayne just proved with his reply. Thanks Wayne, you and others from Eclipse are really helpful and it's been a pleasure to work with you. Ondro Od: Kevin Herron<mailto:[email protected]> Odesláno:úterý 3. října 2017 9:11 Komu: Discussions for new Eclipse projects<mailto:[email protected]> Předmět: Re: [incubation] How do we move github repos from our organisation tothe Eclipse organisation? > From my experience there's no "have to" in Eclipse, only guidelines and best > practices. That may be true in some areas, but I fought hard to avoid squashing history when my project joined Eclipse and lost. I don't think you can avoid it. On Tue, Oct 3, 2017 at 9:04 AM, Ondrej Mihályi <[email protected]<mailto:[email protected]>> wrote: From my experience there's no "have to" in Eclipse, only guidelines and best practices. If you have special needs or concerns, you should discuss with your Eclipse mentor and seek the best for both your project and the Eclipse foundation. They are very flexible, don't be afraid to express your concerns if you think the default isn't convenient for you. Ondro 2017-10-03 8:54 GMT-07:00 Stephane Epardaud <[email protected]<mailto:[email protected]>>: What? We were told we had to squash history when moving… On 03/10/17 17:51, Ondrej Mihályi wrote: As an Eclipse MicroProfile commiter, I know there are 2 options to create a github repo at Eclipse - create a new empty repo based on Eclipse template (EPL license file, etc.) - migrate an existing repo under the Eclipse github org, preserving history, issues and everything else As an example of the second option, have a look at https://github.com/eclipse/microprofile-config - it was migrated under eclipse org this year, but there are still issues and commits dated to 2016 - everything was preserved from day 1. So I wouldn't be afraid of losing history. Ondro 2017-10-03 5:04 GMT-07:00 Oliver Kopp <[email protected]<mailto:[email protected]>>: Hi Stephane, 2017-10-03 13:14 GMT+02:00 Stephane Epardaud <[email protected]<mailto:[email protected]>>: > As part of the Ceylon move to Eclipse, we have to move our github repos to > the Eclipse organisation. I understand we have to delete history, so we'll > need to first force-push a blank history to our current repo, delete all > branches and tags, Yes. You might want to add the tag "initial-code-contribution" as tag. I used "Initial Code Contribution - CQ 7916" at the first commit to ensure proper referencing to IPZilla. I also agree that an BugZilla issue is the best way to move forward. Cheers, Oliver _______________________________________________ incubation mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation _______________________________________________ incubation mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation _______________________________________________ incubation mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation _______________________________________________ incubation mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation
