Given a period of time (e.g. a day, a week, a month), is it possible to list all files that were modified or added in this time?

git: list all files added/modified on a day (or week/month...)

How can i get a list of all the git commits done to the master branch between 2014-01-01 and 2014-06-30?

I know `git log` will give me roughly this format (repeated for all commits):
   
    commit &lt;hash&gt;
    author: &lt;author name&gt;
    date: &lt;date&gt;
    &lt;comment&gt;

But how can it be limited to selected dates and a one line per commit format?

    &lt;hash&gt; &lt;author&gt; &lt;date&gt;
    &lt;hash&gt; &lt;author&gt; &lt;date&gt;

List git commits to master branch between two dates

I&#39;m trying to learn Git with the help of [Git Immersion][1].   
There&#39;s one thing that frustrates me whenever I use `git log` or `git diff`:

![Git log shows (END) marker][2]

I can&#39;t figure out what to do next when I encounter this `(END)` word.

I can&#39;t type any commands, and I end up closing the current Bash window and open another. How do I type in the next command that I want to use?

  [1]: http://gitimmersion.com/
  [2]: http://i.stack.imgur.com/yJ0Ms.png


How to exit git log or git diff

Say I have a file `foo.js` that was committed some time ago. I would like to
simply find the commit where this file was first added.

After reading the answers and my own tinkering, this works for me

&lt;!-- language: sh --&gt;

    git log --follow --diff-filter=A --find-renames=40% foo.js

git - Find commit where file was added

I checked some source code into GIT with the commit message &quot;Build 0051&quot;.

However, I can&#39;t seem to find that source code any more - how do I extract this source from the GIT repository, using the command line?

**Update**

1. Checked in versions 0043, 0044, 0045 and 0046 using SmartGIT.
2. Checked out 0043, and checked in versions up to 0051 on a different branch.
3. Checked out 0043 again.
4. Now, 0051 has disappeared.

**Update**

The source code is definitely there, now its a matter of checking it out:

    C:\Source&gt;git log -g --grep=&quot;0052&quot;
    commit 77b1f718d19e5cf46e2fab8405a9a0859c9c2889
    Reflog: HEAD@{10} (unknown &lt;Mike@.(none)&gt;)
    Reflog message: commit: 20110819 - 1724 - GL: Intermediate version. File version:  v0.5.0 build 0052.
    Author: unknown &lt;Mike@.(none)&gt;
    Date:   Fri Aug 19 17:24:51 2011 +0100

        20110819 - 1724 - GL: Intermediate version. File version: v0.5.0 build 0052.

    C:\Source&gt;

How to search a Git repository by commit message?

I am trying to access a branch&#39;s commit history on a remote repository. I had a look at [the doc][1] but could not find any substantial information on how to access a remote repo&#39;s commit history using my local git client.  


  [1]: http://git-scm.com/book/en/Git-Basics-Viewing-the-Commit-History

Commit history on remote repository

I&#39;ve already looked at the relevant docs from [git-scm.com](http://git-scm.com/book/ch2-3.html) and [gitref.org](http://gitref.org/inspect/), but I can&#39;t seem to figure this out. 

Let&#39;s say I want to get all commits for Tuesday, November 12th, 2013. Using an existing repo as an example, I know for a fact that I have commits on that day, as well as commits the day before and the day after. 

### With `2013-11-11` and `2013-11-12`
All the following give me commits for both November 11th and 12th:

* `git log --after=&quot;2013-11-11&quot; --until=&quot;2013-11-12&quot;`
* `git log --since=&quot;2013-11-11&quot; --until=&quot;2013-11-12&quot;`
* `git log --after=&quot;2013-11-11&quot; --before=&quot;2013-11-12&quot;`
* `git log --since=&quot;2013-11-11&quot; --before=&quot;2013-11-12&quot;`


### With `2013-11-12` only
All the following give me no commits:

* `git log --since=&quot;2013-11-12&quot; --until=&quot;2013-11-12&quot; ` 
* `git log --since=&quot;2013-11-12&quot; --before=&quot;2013-11-12&quot;`
* `git log --after=&quot;2013-11-12&quot; --until=&quot;2013-11-12&quot;`
* `git log --after=&quot;2013-11-12&quot; --before=&quot;2013-11-12&quot;` 

### With `2013-11-12` and `2013-11-13`
As expected (from the results of `2013-11-11` and `2013-11-12` above), all of the following give me results from both November 12th and 13th:

* `git log --since=&quot;2013-11-12&quot; --before=&quot;2013-11-13&quot;`
* `git log --after=&quot;2013-11-12&quot; --before=&quot;2013-11-13&quot;`
* `git log --since=&quot;2013-11-12&quot; --until=&quot;2013-11-13&quot;`
* `git log --after=&quot;2013-11-12&quot; --before=&quot;2013-11-13&quot; `

...and so on and so forth. I feel like I&#39;ve tried every possible combination of `since`, `after`, `before`, and `until` but still can&#39;t find the answer, nor do I understand whether those options are inclusive or exclusive, since they seem to be inclusive if the two dates are different, but exclusive if they&#39;re on the same day. Did I miss something / what am I doing wrong?! 

How do I view all commits for a specific day?

I recently learned that I can get hg log to print the history in reverse order with:

    hg log -r :

So of course I tried:

    git log -r :

Well, it didn&#39;t work. So what is the command to do the same thing in git?

How to git log in reverse order?

Let&#39;s say that I have a graph like this:

    A---B---C---D (master)
         \
          \-E---F (HEAD)

If I do `git log --all --oneline`, I will get all six of my commits.

But if the graph is


    A---B---C---D (master, HEAD)
         \
          \-E---F

I will not see E and F. Can I get git to tell me all the commits, including those on branches which are not named?

Thanks

Get a list of all git commits, including the &#39;lost&#39; ones

The man page says that log shows the commit logs and reflog manages reflog information. What exactly is reflog information and what does it have that the log doesn&#39;t? The log seems far more detailed.

What&#39;s the difference between git reflog and log?

I have a commit c. I want to get the changeset of that exact commit c + metainformation and no other one. Is there a simpler way than `git log -p c^..c` to do that?


git log of a single revision

How can I view the change history of an individual file in Git, complete details with what has changed?

I have got as far as: 

    git log -- [filename]

which shows me the commit history of the file, but how do I get at the content of each of the file changes?

I&#39;m trying to make the transition from Microsoft [Visual SourceSafe][1] and that used to be a simple right-click → *Show history*.

  [1]: https://en.wikipedia.org/wiki/Microsoft_Visual_SourceSafe


View the change history of a file using Git versioning

How can I configure `git log` to show `commit date` instead of `author date`?


How to configure &#39;git log&#39; to show &#39;commit date&#39;

Let&#39;s say I created a new branch `my_experiment` from  `master` and made several commits to `my_experiment`. If I do a `git log` when on `my_experiment`, I see the commits made to this branch, but also the commits made to `master` before the `my_experiments` branch was created.

I would find it very useful to see the history of all commits to the `my_experiments` branch until it hits the creation of that branch - effectively a true history of just that branch. Otherwise it&#39;s not clear to me when looking through the log whether the commits were on the `my_experiments` branch or not.

Is there a way to do this with Git?


How to get commit history for just one branch?

With Subversion I could use [TortoiseSVN][1] to view the history/log of a file.

How can I do this with Git?

I am just looking for the history record for a particular file, and then the ability to compare the different versions.

  [1]: https://en.wikipedia.org/wiki/TortoiseSVN



How can I view file history in Git?

Or just all the commits that occurred between two dates? In SVN, you could do something like 

    svn diff -r{date}:{date}

to do it! I can&#39;t seem to find a Git equivalent to this.

Specifically I&#39;m looking at writing a script to send out daily emails with all the code committed that day and by who.

How can I get the diff between all the commits that occurred between two dates with Git?

I&#39;m on a branch with some changes.  Changing branch is a pain as some files are locked by processes, so to change branch I&#39;d have to stop all the processes which have locks, then `stash` the changes before checking out the other branch to see its log.

Is it possible to view the log for a different branch, without having to check it out?

How can I print the log for a branch other than the current one?

I&#39;m trying to view commits made by a specific user, and want to remove any  merges done by the user from the output. How can I do so?

I can check for the commits of a user using `git log --author=&lt;name&gt;`, but can&#39;t remove the merge commits in the output.

PS: Merge conflicts do not happen in the workflow of the repo in question, all branches are rebased before merging into master so it is safe to remove the merge commits from the output, and similarly, two feature branches are not merged with one another raising the possiblity.

View git log without merge commits

I have a deleted line in a file in my Git repository. I knew some of the missing text, and the file that it was in, so I used `git log -S&#39;missingtext&#39; /path/to/file`.

However, the only thing that came back was the commit in which I added the line containing the missing text. The text wasn&#39;t present in HEAD, and the commit that added it was present in my branch, so I knew that one of the commits in my branch&#39;s history must have removed it, but it wasn&#39;t showing up.

After some manual searching, it turned out that the line was removed accidentally while resolving a conflict for a merge. So I&#39;m wondering:

1. Is this the reason why pickaxe couldn&#39;t find the commit that deleted the line?
2. How could I have found where &quot;missingtext&quot; was deleted without digging through the history manually?

Any insight on #1 would be great (I assumed that `git log -S` would give me my answer), but my real question is #2 since I&#39;d like to be able to avoid this in the future.







How to find commit when line was deleted/removed?

When you run `git log --decorate --pretty=oneline` the output will have entries like `(HEAD, refs/published/master, master)` with coloration.

I also have the following in my gitconfig:

    [color &quot;branch&quot;]
        current = yellow reverse
        local = yellow
        remote = green


How do you replicate those colors when doing a custom format like the following?

    git log --decorate --stat --graph --pretty=format:&quot;%d %Cgreen%h%Creset (%ar - %Cred%an%Creset), %s%n&quot;

Color in git-log

In the git community book, it says

&gt; Another interesting thing you can do is visualize the commit graph with the &#39;--graph&#39; option, like so:
&gt;
    $ git log --pretty=format:&#39;%h : %s&#39; --graph
    * 2d3acf9 : ignore errors from SIGCHLD on trap
    *   5e3ee11 : Merge branch &#39;master&#39; of git://github.com/dustin/grit
    |\
    | * 420eac9 : Added a method for getting the current branch.
    * | 30e367c : timeout code and tests
    * | 5a09431 : add timeout protection to grit
    * | e1193f8 : support for heads with slashes in them
    |/
    * d6016bc : require time for xmlschema

&gt; It will give a pretty nice ASCII representation of the commit history lines.

How should I read this graph? How does `420eac9` differ from the rest?

How to read git log graph

Some Git commands take commit ranges and one valid syntax is to separate two commit names with two dots `..`, and another syntax uses three dots `...`.

What are the differences between the two?


What are the differences between double-dot &quot;..&quot; and triple-dot &quot;...&quot; in Git commit ranges?

I have a local branch tracking the remote/master branch. After running `git-pull` and `git-log`, the log will show all commits in the remote tracking branch as well as the current branch. However, because there were so many changes made to the remote branch, I need to see just the commits made to the current local branch.

What would be the Git command to use to only show commits for a specific branch?

Notes:

Configuration information:

    [branch &quot;my-branch&quot;]
      remote = origin
      merge = refs/heads/master


How do I run git log to see changes only for a specific branch?

Suppose your git commit history looks like this:

    A---B---C---D---E---F master
         \         /
          X---Y---Z topic

Is it possible to have git list only the commits on master, A-F? In other words, if the commit was on a merged-in branch, I don&#39;t want it show.

Git: How to list commits on this branch but not from merged branches

I&#39;ve renamed a couple of files using `git mv`, used `git stash`, had a quick look at HEAD (without changing it) then did `git stash pop` to get the whole lot back again. My moves had disappeared from the commit list, so I redid them with `git rm` and the commit message claimed git had spotted the rename was a rename. So I thought no more of it.

But now, post-commit, I can&#39;t get at the history of the moved files! Here&#39;s what git says about the commit in question:

    ~/projects% git log --summary
    commit de6e9fa2179ae17ec35a5c368d246f19da27f93a
    Author: brone
    Date:   Wed Dec 8 22:37:54 2010 +0000
    
        Moved R_DebugUI into runtime
    
     delete mode 100644 test/R_DebugUI_iOS.h
     delete mode 100644 test/R_DebugUI_iOS.m
     create mode 100644 system/runtime/src/R_DebugUI_iOS.h
     create mode 100644 system/runtime/src/R_DebugUI_iOS.m

     &lt;&lt;snip older commits&gt;&gt;
     ~/projects%

I&#39;m now trying to get the history of one of these moved files, so I can look at an old version, but I don&#39;t get anything very useful:

    ~/projects/system/runtime/src% git log --follow --find-copies-harder -M -C R_DebugUI_iOS.m
    commit de6e9fa2179ae17ec35a5c368d246f19da27f93a
    Author: brone
    Date:   Wed Dec 8 22:37:54 2010 +0000
    
        Moved R_DebugUI into runtime
    ~/projects/system/runtime/src% 

(I&#39;ve also tried it without `-M`, `-C` and `--find-copies-harder`, but to no avail.)

I can get its history under its old name, which stops at the point it was deleted from its old location:

    ~/projects% git log --summary --follow --find-copies-harder -M -C -- test/R_DebugUI_iOS.m
    commit de6e9fa2179ae17ec35a5c368d246f19da27f93a
    Author: brone
    Date:   Wed Dec 8 22:37:54 2010 +0000
    
        Moved R_DebugUI into runtime
    
     delete mode 100644 test/R_DebugUI_iOS.m
    
    commit 32a22d53c27e260714f759ecb3d3864e38b2e87f
    Author: brone
    Date:   Tue Dec 7 23:52:51 2010 +0000
    
        Can set debug UI&#39;s alpha.
    
    &lt;&lt;snip older commits&gt;&gt;
    ~/projects%

So I&#39;m not completely stuck this time, but I wouldn&#39;t fancy having to do this kind of thing all the time. (I anticipate having a fair number of files that will move at least once in their life.)

Am I doing something wrong? The old copy of the file and the new copy are 98.8% the same (2 lines out of 166 changed). My understanding is that git should be able to track the file in this case, because it infers rename operations rather than storing them explicitly, and the files are similar enough that I believe it should consider them the same.

Is there anything I can do to fix this?


Why might git log not show history for a moved file, and what can I do about it?

I have a simple test repository with just several commits and want to see the date&amp;time filtered log:

&lt;pre&gt;
$ git log --author=&quot;automatix&quot; --since=&quot;2013-01-30&quot; --pretty -- test
commit ea0719bef142659fa561c9d040b2120012ed0184
Date:   Thu Jan 31 02:03:12 2013 +0100

commit ab4a8387bc4d9bdb4f67212df77eb1fc3d8b6304
Date:   Thu Jan 31 01:59:11 2013 +0100

commit a0b027beba2cd03571bb9475b9db9542f8efe990
Date:   Thu Jan 31 01:50:38 2013 +0100

commit add77c8fe2ba9254c11b98e14facede3420dc51c
Date:   Thu Jan 31 01:48:34 2013 +0100

commit e6e323c05d37c74fcabeb9186b95c0d49b862e6f
Date:   Thu Jan 31 01:46:27 2013 +0100

commit 8c286391e54d3fc1e210950b1320fd6f013a8f84
Date:   Thu Jan 31 01:41:27 2013 +0100

commit 9c880595e57f717383796fa2940f41f0f42f7e2a
Date:   Thu Jan 31 01:38:17 2013 +0100

commit a95527f36a533e1ecba1aadceea31a9dcbe1a8db
Date:   Thu Jan 31 01:30:00 2013 +0100
&lt;/pre&gt;
The first selected commit is `a95527f36a533e1ecba1aadceea31a9dcbe1a8db` from `2013-01-30 01:30:00`. 8 commits are selected:
&lt;pre&gt;
$ git log --author=&quot;automatix&quot; --since=&quot;2013-01-30&quot; --format=oneline -- test | wc
      8      34     498
&lt;/pre&gt;
OK. Now I select since `2013-01-31`:
&lt;pre&gt;
$ git log --author=&quot;automatix&quot; --since=&quot;2013-01-31&quot; --format=oneline -- test | wc
      0       0       0
&lt;/pre&gt;

What? Ok, that should mean, that the `since` rule *excludes* the commits of the startdate. Right?

But let&#39;s go on:

&lt;pre&gt;$ git log --author=&quot;automatix&quot; --since=&quot;2013-01-31 01:30:00&quot; --pretty -- test
commit ea0719bef142659fa561c9d040b2120012ed0184
Date:   Thu Jan 31 02:03:12 2013 +0100

commit ab4a8387bc4d9bdb4f67212df77eb1fc3d8b6304
Date:   Thu Jan 31 01:59:11 2013 +0100

commit a0b027beba2cd03571bb9475b9db9542f8efe990
Date:   Thu Jan 31 01:50:38 2013 +0100

commit add77c8fe2ba9254c11b98e14facede3420dc51c
Date:   Thu Jan 31 01:48:34 2013 +0100

commit e6e323c05d37c74fcabeb9186b95c0d49b862e6f
Date:   Thu Jan 31 01:46:27 2013 +0100

commit 8c286391e54d3fc1e210950b1320fd6f013a8f84
Date:   Thu Jan 31 01:41:27 2013 +0100

commit 9c880595e57f717383796fa2940f41f0f42f7e2a
Date:   Thu Jan 31 01:38:17 2013 +0100

commit a95527f36a533e1ecba1aadceea31a9dcbe1a8db
Date:   Thu Jan 31 01:30:00 2013 +0100
&lt;/pre&gt;

&lt;pre&gt;$ git log --author=&quot;automatix&quot; --since=&quot;2013-01-31 01:30:00&quot; --format=oneline -- test | wc
      8      34     498
&lt;/pre&gt;

Now, when I&#39;m writing the starttime as well, the commits of the starttime are *included* .

I don&#39;t understand the logic. Can anybody explain, why it works so strange?

Thanks

How does git log --since count?

How can I view any local commits I&#39;ve made, that haven&#39;t yet been pushed to the remote repository? Occasionally, `git status` will print out that my branch is X commits ahead of `origin/master`, but not always.

Is this a bug with my install of Git, or am I missing something?

Viewing unpushed Git commits

I have a Git alias that expands to:

    git log --graph --oneline --all --decorate

According to `man git log` there are a couple of suspicious options: `--not` and `--branches`; but I can&#39;t make it work properly.

How should I edit that to hide the stashes?

---

**FYI**: as per the [accepted question][1] and [comment][2] my `.gitconfig` alias now looks like this:

    [alias]
        l = log --branches --remotes --tags --graph --oneline --decorate --notes HEAD


[1]: https://stackoverflow.com/a/9438578/477168
[2]: https://stackoverflow.com/questions/9437182/git-show-all-branches-but-not-stashes-in-log#comment46034208_9438578

Git show all branches (but not stashes) in log

Is there a way to see with `git log` or some other command only the commits that were added after branch creation?

    usage: git log [&lt;options&gt;] [&lt;since&gt;..&lt;until&gt;] [[--] &lt;path&gt;...]
       or: git show [options] &lt;object&gt;...
    
        --quiet               suppress diff output
        --source              show source
        --decorate[=...]      decorate options

show commits since branch creation

My repository underwent changes such as:

1. ...some unrelated commits...
1. Commit new file `foo` with 100 lines of content
1. ...intervening commits, some of which touch `foo`...
1. Insert the contents of `foo` at the top of an existing file `bar` and `git rm foo` in the same commit
1. ...more unrelated commits...

Now I want to see the log of deleted file `foo`.  Everything I&#39;ve read, including on SO, says I should be able to `git log -- foo`, but that command produces no output.

If I find the commit that includes deleting `foo` I can `git log 1234abcd -- foo` and see its log, so I think my path to `foo` isn&#39;t the problem.  Also note that `git merge-base HEAD 1234abcd` outputs `1234abcd[...]`, so I think that should prove the commit is reachable from `HEAD`.  Note that there is no file `foo` in my working tree (obvious, since it was deleted).  Using Git 1.7.1.1 on OS X.

Why doesn&#39;t `git log -- foo` work for me and how can I fix it?  Thanks!

Why doesn&#39;t &quot;git log -‌- foo&quot; work for deleted file foo?

How can I move a directory and files to a sub-directory along with commit history?

For example:

* Source directory structure: `[project]/x/[files &amp; sub-dirs]`

* Target directory structure: `[project]/x/p/q/[files &amp; sub-dirs]`


Move file and directory into a sub-directory along with commit history

I need some help. It is possible to only show one commit id? Since git log -3 show the log from 1 - 3, I just want to show only 3. What possible command will match for it?

I use the command

           git log -3 --pretty=format:&quot;%h&quot;

the result is
 
           ffbef87
           cf0e073
           1c76c5d

I only want to display the **1c76c5d** only.

            

git log show one commit id only

I&#39;m on branch-X and have added a couple more commits on top of it. I want to see all the differences between MASTER and the branch that I am on in terms of commits. I could just do a 

    git checkout master
    git log

and then a 

    git checkout branch-X
    git log

and visually diff these, but I&#39;m hoping for an easier, less error-prone method.

How do I see the commit differences between branches in git?

I want to be able to see all of the commits I made today using `git log`. I came up with `git log --after=&quot;yesterday&quot;`  
However, that seems a little awkward to me, is there a simpler command to achieve the same effect?

How to make Git log show all of today&#39;s commits?

Several times, I have come across the statement that, if you move a single function from one file to another file, Git can track it. For example, [this entry][1] says, &quot;Linus says that if you move a function from one file to another, Git will tell you the history of that single function across the move.&quot;

But I have a little bit of awareness of some of Git&#39;s under-the-hood design, and I don&#39;t see how this is possible. So I&#39;m wondering ... is this is a correct statement? And if so, how is this possible?

My understanding is that Git stores each file&#39;s contents as a Blob, and each Blob has a globally unique identity which arises from the SHA hash of its contents and size. Git then represents folders as Trees. Any filename information belongs to the Tree, not to the Blob, so a file rename for example shows up as a change to a Tree, not to a Blob.

So if I have a file called &quot;foo&quot; with 20 functions in it, and a file called &quot;bar&quot; with 5 functions in it, and I move one of the functions from foo into bar (resulting in 19 and 6, respectively), how can Git detect that I moved that function from one file to another?

From my understanding, this would cause 2 new blobs to exist (one for the modified foo and one for the modified bar). I realize a diff could be calculated to show that the function was moved from one file to the other. But I don&#39;t see how history about the function could possibly become associated with bar instead of foo (not automatically, anyway).

If Git were to actually look *inside* of single files, and compute a *blob per function* (which would be crazy / infeasible, because you&#39;d have to know how to parse any possible language), then I could see how this might be possible.

So ... is the statement correct or not? And if it is correct, then what is lacking in my understanding?


  [1]: https://stackoverflow.com/questions/1598759/git-and-mercurial-compare-and-contrast/1598812#1598812/

Can Git really track the movement of a single function from 1 file to another? If so, how?

I&#39;ve seen some books and articles have some really pretty looking graphs of Git branches and commits. How can I make high-quality printable images of Git history?


Pretty Git branch graphs

How can I have a list with all the files that were changed in the last 2 days? I know about 
    
    git log --name-status --since=&quot;2 days ago&quot; 

but this will show me ids, dates and commit messages. All I need is the list of the file names which were changed.

Is that possible with git?

Git show files that were changed in the last 2 days

Let&#39;s say I have a Git repo with branch `A` and branch `B`.  
Branch `B` is currently checked out (i.e. `.git/HEAD` contains `refs/heads/B`).  
Now, **without checking out branch `A`**, how to view the history (log) of `path/file` in branch `A`?

Following `git help rev-parse`, I&#39;ve attempted to use `git log A:path/file`, but that doesn&#39;t seem to work (outputs nothing). Why?

How to `git log` a tree-ish from another branch?

I have 2 branches A and B.

Whenever I run a build, Branch A gets merged into Branch B. I want to be able to email out all the updates made in A, since the last time the build was ran.  How can I use `git log` to be able to copy all the commits made in A since the last A -&gt; B merge?

git log the difference between 1 branch from another

I&#39;m trying to use tags for release management in Git—I create a tag for each release. I&#39;d like to be able to create release notes by listing the comment titles for every commit since a tag, or between 2 tags. I can&#39;t seem to find any way to do this.

How do I show just the names and commit titles since a tag in Git?

If `my-feature-branch` was merged into `my-main-branch`, how can I see what commits were merged in from `my-feature-branch`?

How to see commits that were merged in to a merge commit?

I would like to see all stashes in `git log` output. Does anyone know if there is a way to do that?

Edit: I want to see all commits in the log -- *including* stash commits. I tried the command:

    git log --date-order --all

But it returns only the top most stash. I would like to see commits that represent other stashes too.

Show all stashes in git log

When using `git log`, how can I filter by user so that I see only commits from that user?

How can I view a git log of just one user&#39;s commits?

Here is my case:

 - I was working on one branch.
 - Pushed new commits to the remote.
 - Switched back to the master branch. 

But suddenly after typing `git checkout master` command my computer encountered [blue screen of death][1] and an unexpected force shut down happened. After starting back my computer I have checked the status of my current branch and as a result I got each and every file as marked new files.

Now, I am stuck at this point and after `git log` command I am getting error 

    $ git log
    fatal: your current branch appears to be broken

How to solve this problem and recover my branch?.

I am working with windows 7 and git bash latest version

&gt; Edit: **I don&#39;t want to delete this branch.**


  [1]: https://en.wikipedia.org/wiki/Blue_Screen_of_Death

Broken branch in git, fatal: your current branch appears to be broken

I use a fairly complex `git-log` command involving `--date-order` to get an overview of my repository&#39;s status; but unfortunately, `--date-order` seems to use the *committer* date, not the *author* date. That means that each time I bring my topic branches up to date by rebasing them onto the current upstream, I lose the helpful chronological ordering in my `git-log` of relative commits in my topic branches (that is, each branch becomes a single long line, because all of its commits got rebased to sequential and nearly-identical committer timestamps.)

If I could get `git-log` to order commits by the *author* timestamp instead of the *committer* timestamp, this would be solved. Does anybody know of a way to do that?

----

For those visiting this from Google results, you may want to look into [josephdpurcell](https://stackoverflow.com/users/990642/josephdpurcell)&#39;s solution (and [in-depth blog post](http://thesimplesynthesis.com/post/how-to-sort-git-commits-by-author-date/)!), below. It&#39;s quite excellent, if you&#39;re looking for standard `git-log` style output, multi-line, with detailed messages about each commit.

Unfortunate, I now need to amend this question, because I&#39;m an idiot and didn&#39;t provide more specific information about my use-case: I use `git-log` in “`--graph` mode,” and I need to make **`git-log` itself** operate in author-date-order. As far as I&#39;ve been able to ascertain, this is completely impossible to do from outside `git-log`, because `git-log` *itself* handles the graph ordering and printing.

A script, or patch for `git-log`, may be necessary, it seems. I&#39;ll leave this open until somebody can either 1. write such a script, or 2. we can talk the `git` authors into including a `--author --date-order` combination of flags. (=

----

For reference, here&#39;s what my current [`glog` function](https://github.com/elliottcable/System/blob/Master/Dotfiles/profile#L180-L189)&#39;s output looks like, and what I need to re-order:

![glog output](http://i.stack.imgur.com/HUVAU.png)

All Git Log Solutions on Gang of Coders

Total of 45 Git Log Solutions