You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: