git-commit

I'm converting everything over to Git for my own personal use and I found some old versions of a file already in the repository. How do I commit it to the history in the correct order according the the file's "date modified" so I have an accurate history of the file? I was told something like this would work: git filter-branch --env-filter="GIT_AUTHOR_DATE=... --index-filter "git commit path/to/file --date " --tag-name-filter cat -- --all Chris Johnsen The advice you were given is flawed. Unconditionally setting GIT_AUTHOR_DATE in an --env-filter would rewrite the date of every commit. Also,

I've got a script that needs to reference the initial commit in a repository. git has the special reference HEAD , but doesn't have the corresponding TAIL . I cannot find anything in git help rev-parse that would seem to help me. Here's what I'd like to do: git show TAIL Here's one option I have: git show `git log --reverse | if read a commit ; then echo $commit ; fi` That's pretty hacky and depends on the output of git log not changing. Right now I just tag the initial commit and use that as my refspec. However, I'd like to release a general tool, so that's not a great option. Jakub Narębski

I added some files to the index but then by mistake I deleted them with git reset --hard . How do I recover them? Here's what happened: I added all files using git add . I then committed When I checked the status, there were still files that weren't included in the commit from the add, which was strange I added the untracked files again and it worked this time But I wanted everything to be in 1 single commit so I looked up how to unstage what I just committed I used git reset --hard HEAD^ — bad idea obviously, all files were deleted so then I used git reflog to find where I left off then I

How does this actually come about? I am working in one repo by myself at the moment, so this is my workflow: Change files Commit Repeat 1-2 until satisfied Push to master Then when I do a git status it tells me that my branch is ahead by X commits (presumably the same number of commits that I have made). Is it because when you push the code it doesn't actually update your locally cached files (in the .git folders)? git pull seems to 'fix' this strange message, but I am still curious why it happens, maybe I am using git wrong? including what branch is printed in the message My local branch is

I have seen GIT commit --amend in detached HEAD state . The question requires the answer to be more complex than needs be. I'd like to understand just how git commit --amend works in a normal HEAD situation. Assume that you're in a clean working state and that your repo looks as follows: If you then run git commit --amend write a commit message, save and quit your editor, the following happens: Your staging area—which, if you haven't staged any new changes, will be identical to commit f42c5 —is used to create a new commit: 31b8e . Its parent(s) will be the same as that(those) of the commit you