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

Tip to recover lost commit #32

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Tip to recover lost commit #32

wants to merge 1 commit into from
+11 −1

Conversation

princejwesley
Copy link

commit contains:

  1. Tip to recover lost commit
  2. 'Purne' typo fix

@hemanth
Copy link
Contributor

hemanth commented Aug 30, 2015

We would need more than just git reflog

@princejwesley
Copy link
Author

We would need more than git reflog to apply (reset or cherry-pick) or view (show or diff) lost/old commit object. Imho, git flog is sufficient to recover those commit hash.

hemanth
hemanth reviewed Aug 30, 2015
View reviewed changes
README.md
@@ -383,5 +384,10 @@ __Alternatives:__
git remote prune origin
```

## Recover lost commits in the local branches or get information about the state of old branches
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would make sense if it were to be -> ## Visualize each position of HEAD in the last 30 days.

@hemanth
Copy link
Contributor

hemanth commented Oct 22, 2015

@princejwesley You would mind rebasing?

@ramsedsay
Copy link

Thanks guys I need some more money.

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

Successfully merging this pull request may close these issues.

None yet
3 participants
@princejwesley @hemanth @ramsedsay