-
Notifications
You must be signed in to change notification settings - Fork 96
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
Disappearing commits? #24
Comments
No known force pushes from me! Ugh, sorry.
I do have a mirror with git.howett.net; perhaps that is broken.
…On Mar 21, 2017 5:33 AM, "Karol Woźniak" ***@***.***> wrote:
It seems that my changes from #19
<#19> went into abyss.
You're not --force pushing to master, are you :-)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALjBmCHyaaG2Pg_0HTkwar6w5ZZJ9n0ks5rn8OdgaJpZM4MjuyQ>
.
|
@KenjiTakahashi Terribly sorry about that. It does look like the gitolite mirror stomped the commits. I reintroduced your patch and tests with 445e867. I hope nothing else got sucked into the abyss with it. Would you mind checking your git history? |
Looks fine on my side now, cheers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that my changes from #19 went into abyss.
You're not
--force
pushing to master, are you :-)?The text was updated successfully, but these errors were encountered: