Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate branches #27

Closed
Minoru opened this issue Jun 27, 2017 · 2 comments
Closed

Migrate branches #27

Minoru opened this issue Jun 27, 2017 · 2 comments
Labels
enhancement
Milestone
0.5

Comments

@Minoru
Copy link
Collaborator

Minoru commented Jun 27, 2017

Split from #6.

We should rewrite all the commits that are reachable from all branches, and then migrate those branches onto new commit IDs. There's no point in migrating just master.
@Minoru Minoru added this to the 0.5 milestone Jun 27, 2017
@Minoru Minoru mentioned this issue Jun 27, 2017
Open
2 tasks
Minoru added a commit that referenced this issue Jun 28, 2017
@Minoru
Migrate branches (#27)
fa4d3f3 
Breaks final checkout, but we can live with that for now.
@Minoru
Copy link
Collaborator Author

Minoru commented Jun 28, 2017

Migration is done, but the final checkout is now broken. I don't consider this a release blocker because a user can still run git reset --hard; dropping the milestone, will add a note to CHANGELOG in a moment.

@Minoru Minoru removed this from the 0.5 milestone Jun 28, 2017
@Minoru
Copy link
Collaborator Author

Minoru commented Jun 30, 2017

The regression was fixed by e4a81ac; adding the issue back to the milestone and closing it as fixed.

@Minoru Minoru closed this as completed Jun 30, 2017
@Minoru Minoru added this to the 0.5 milestone Jun 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
0.5
Development

No branches or pull requests
1 participant
@Minoru