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

master was force pushed by accident 2015-02 #167

Open
MarcWeber opened this issue Feb 15, 2015 · 1 comment
Open

master was force pushed by accident 2015-02 #167

MarcWeber opened this issue Feb 15, 2015 · 1 comment

Comments

@MarcWeber
Copy link
Owner

Thus people who have updated/fetched VAM from approx 2015-02-11 to 2015-02-15 may see "forced update" in git pull logs or get some strange merge history. The "wrong" master (98b7144) which was available doesn't do any harm, it just dropped some of more recent commits and contained #164 which doesn't really affect VAM's behaviour. If you ran into this "issue" you can git reset --hard origin/master to continue following current upstream.

How long to keep this? I'd say at least 3 month. Should this even be moved into README? I'm unsure. Let us know, please!
@MarcWeber MarcWeber changed the title master was changed by accident. master was force pushed by accident 2015-02 Feb 15, 2015
@ZyX-I
Copy link
Collaborator

ZyX-I commented Feb 15, 2015

#164 merge was pushed only around 5 hours ago. Prior to that master was 63efd3b which is why #166 was reported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MarcWeber @ZyX-I