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

IMPORTANT: Rewriting history of repository #35

Closed
alexandru opened this issue Jan 15, 2016 · 2 comments
Closed

IMPORTANT: Rewriting history of repository #35

alexandru opened this issue Jan 15, 2016 · 2 comments

Comments

@alexandru
Copy link
Owner

This is of special interest to @Peranikov, @piruty-joy, seeing that they are working on a Japanese translation. And for anybody else with active forks.

I've rewritten the whole history of the project to hide my emails behind noreply@alexn.org. This is because GitHub has become a spam problem for me and I do not want to expose my real emails anymore. I've followed the tutorial here and have only touched my own commits: https://help.github.com/articles/changing-author-info/

Existing forks have to rebase off the new master, otherwise your branch is going to be divergent. The recipe for doing that goes something like this:

  1. BACKUP
  2. DO NOT start with a git pull
  3. git fetch
  4. git rebase --onto origin/master master <local_branch> (for local each branch)
  5. git pull --force

Sorry for the inconvenience and let me know if you need help.

@Peranikov
Copy link

Hi @alexandru.

Thank you for your message. I updated my fork repository.
Please your continuous support.

sincerely,

Peranikov

@alexandru
Copy link
Owner Author

I'm closing this.

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

2 participants