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.

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

Commit hashes between 1.15.1837.102 and 2.17.2095.102 are going to be changed. #290

Closed
yukawa opened this issue May 17, 2015 · 0 comments
Closed

Comments

@yukawa
Copy link
Collaborator

yukawa commented May 17, 2015

If you have never cloned Mozc repository from GitHub, you can stop reading now.
If you have cloned Mozc repository from GitHub and its HEAD is 2.17.2096.102 or newer, you can stop reading now.
In other cases, you need to clone Mozc repository from GitHub again.

In order to complete Subversion to Git migration, we plan to do force-push which updates several previous commit messages. As a result, commit hashes after 1.15.1837.102 will be changed. No file content except for commit hashes written in Release History will be changed in this force-push.

We do understand that we should not update previous commits in public repository in general, and we do hope that we never have to do this again. We apologize for any inconvenience this may have caused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant