Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As you might have known that by default, git doesn’t enable reflog updates for new bare repositories. The problem is, I have a long history repository but it was created before I set the flag “logAllRefUpdates” on, and now I want that information for another application to work.
How can I achieve that with minimal changes made to the existing repository. A very simple solution is pushing a new commit which I don’t want to (!) 🙂
The reflog is a relatively simple file format. Here’s an example:
You can manually construct appropriate reflogs by following the same format:
Just create one of these for each ref. You can probably do this directly with
git for-each-refwith an appropriate format string (thanks, Chris!)