Migrate to Git
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MadGraph5_aMC@NLO |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
This isn't really a bug but an offer of some code and help.
I've been trying to help someone with this program and struggling to parse through the different branches and waiting hours for checkouts of branches to download so I wrote a script to migrate all the branches and revisions to git where I can more easily review branches and see what was going on in the project.
Obvious I don't know the projects goals in this regard but I wanted to offer the solution up if it was a pain point for the project as well or something that was be considered.
The script is posted here:
https:/
The migrated code(and some of my tinkerings) are here:
https:/
Its I think a pretty straightforward python script. Not really polished or anything just hacked on until it worked and pushed up. It currently migrates everything that comes up in launchpad's branches list but its just a python script so it could easily be modified to filter out branches that aren't wanted.
I'm also happy to help with running the migration, setting up a project in gitlab/github, etc, just let me know.
Changed in mg5amcnlo: | |
importance: | Undecided → Wishlist |
Changed in mg5amcnlo: | |
status: | New → Fix Released |
Hi,
This is a project that is quite interesting but which is for me quite complicated to do.
And for the moment, I need to focus on the python3 conversion before looking how to do the bzr to git conversion.
The issue when doing such conversion is obviously to keep all the branch history in place and be sure that we can still merge efficiently branches that have started to diverge more than 5 years ago.
What worries me in your code is first his README:" Currently broken by relying on git bzr plugin which runs into buts with bugs in bzr and fast-export. Something you posted to github but was thrown back at bzr."
Then do you have an example where you load various bzr branches into a single git repo?
I think the real issue here is to be sure that we can load all the branches in a consistent way and that we can efficiently merge them afterwards. This validation is actually what would take a lot of time to be convince that we have a tools that allow a clean transition. If you can do such careful validation that would be awesome.
Cheers,
Olivier