blocks|key|1283995|text|您可以使用git+whatchanged+--since="1+day+ago"+-p|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1283996|它还需要一个--until参数。|1283997|Docs|1283998|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/docs/git-whatchanged/1.7.9^0|5|12|0|6|7|0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

You could use <code>git whatchanged --since="1 day ago" -p</code>

It also takes a <code>--until</code> argument.

<a href="http://git-scm.com/docs/git-whatchanged/1.7.9" rel="noreferrer">Docs</a>

blocks|key|1284051|text|"date“在git中是一个有点松散的概念。提交将有一个作者日期，这可能是在某人实际将提交拉入/提交到其存储库之前的一段时间，而且提交可能会被重新定位并更新为位于明显较新的提交之上。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1284052|提交还有一个提交日期，如果以任何方式改变提交基数或修改提交，提交日期都会更新。这些提交更可能是按某种时间顺序进行的，但您仍然受制于提交者在其计算机上设置了正确的时间，即使如此，未修改的提交在合并到中央存储库的主分支之前，可以无限期地位于远程存储库的功能分支上。|1284053|对于您的目的来说，最有用的可能是特定存储库上的reflog日期。如果您启用了每个分支的reflog(请参阅git+config+core.logAllRefUpdates)，那么您可以使用ref@{date}语法来引用分支在特定时间的位置。|offset|length|style|CODE|1284054|例如。|1284055|git+log+-p+master@{2009-07-01}..master@{now}|code-block|syntax|javascript|1284056|您还可以使用‘模糊’描述，如：|1284057|git+log+-p+"master@{1+month+ago}..master@{yesterday}"|1284058|这些命令将显示在给定的存储库分支中“出现”的所有提交，而不管它们根据其作者和提交日期实际有多“旧”。|1284059|请注意，每个分支的reflog是特定于存储库的，所以如果您在克隆上运行log命令，并且您没有拉取(比方说)一个月，然后一次拉取上个月的所有更改，那么上个月的所有更改都将出现在一个@{1+hour+ago}..@{now}范围内。如果您能够在人们推送到的“中心”repostory上运行log命令，那么它可能会执行您想要的操作。|1284060|entityMap^0|0|0|1H|W|2M|A|0|0|0|0|0|0|2H|L|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@$F|13|G|14|H|I]|$F|15|G|16|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|18|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|1A|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Z|$]]

"date" is a bit of a loose concept in git. A commit will have an author date that may be some time well in the past before someone actually pulls/commits the commit into their repository, also the commit may be rebased and updated to be on top of an apparently newer commit.

A commit also has an commit date which is updated if a commit is rebased or amended in any way. These commits are more likely to be in some sort of chronological order but you are still at the mercy of the committer having the correct time set on his computer and even so, an unmodified commit can sit on a feature branch on a remote repository indefinitely before being merged into the master branch of a central repository.

What is probably most useful for your purposes is the reflog date on the particular repository in question. If you have per-branch reflogs enabled (see <code>git config core.logAllRefUpdates</code>) then you can use the <code>ref@{date}</code> syntax to refer to where a branch was at a particular time.

E.g.

<pre><code>git log -p master@{2009-07-01}..master@{now}
</code></pre>

You can also use 'fuzzy' descriptions like:

<pre><code>git log -p "master@{1 month ago}..master@{yesterday}"
</code></pre>

These commands will show all commits that have 'appeared' in the given branch of the repository regardless of how 'old' they actually are according to their author and commit dates.

Note that the per-branch reflog is specific to a repository, so if you're running the log command on a clone, and you don't pull for (say) a month then pull all the changes for the last month at once, then all of the last month's changes will appear in a <code>@{1 hour ago}..@{now}</code> range. If you are able to run the log command on the 'central' repostory that people push to, then it may do what you want.

blocks|key|1498938|text|您还可以使用git-format-patch准备补丁程序(diffs)并通过电子邮件发送它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1498939|使用选项自或修订范围来指定提交范围。|1498940|entityMap|0|LINK|mutability|MUTABLE|url|http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html^0|6|G|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You can also use <a href="http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html" rel="nofollow noreferrer">git-format-patch</a> to prepare patches (diffs) and send them through email.

Use options [since] or [revision range] to specify commits range.

blocks|key|1284136|text|也许吧|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1284137|$+git+format-patch+--committer=<who>+--since=yesterday+--stdout|code-block|syntax|javascript|1284138|是你想要的吗(不管有没有'--stdout')？|1284139|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Perhaps

<pre><code>$ git format-patch --committer=&lt;who&gt; --since=yesterday --stdout
</code></pre>

is what you want (with or without '--stdout')?

blocks|key|1284181|text|我认为一般的解决方案是使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1284182|git+rev-list+-n1+--first-parent+--until=<a+date+string>+<a+ref>|code-block|syntax|javascript|1284183|如果没有--first-parent，您可能会从一个后来合并到a+ref中但在a+date+string之前还没有合并的分支中获得提交。|offset|length|style|CODE|1284184|下面是使用--children和grep而不是-n1的替代方案|1284185|mlm_git_ref_as_of()+{
++++#+#+Examples+#
++++#
++++#+Show+all+commits+between+two+dates:
++++#
++++#+++++git+log+$(mlm_git_ref_as_of+'2012-05-21+09:00:00-0400')..$(mlm_git_ref_as_of+'2012-05-21+17:00:00-0400')
++++#
++++#+Show+diffs+of+all+commits+between+two+dates:
++++#
++++#+++++git+diff+$(mlm_git_ref_as_of+'2012-05-21+09:00:00-0400')..$(mlm_git_ref_as_of+'2012-05-21+17:00:00-0400')
++++local+as_of="$1"
++++local+ref="${2:-HEAD}"
++++#+Get+the+most+recent+commit+(--children,+grep+-v+'+')+that+was+on
++++#+the+given+branch+($ref,+--first-parent)+as+of+a+given+date
++++#+($as_of)
++++git+rev-list+--children+--first-parent+--until="$as_of"+"$ref"+%7C+grep+-v+'+'
}|1284186|在阅读这篇问答之前，我对git+whatchanged并不熟悉，但它给了我非常不同的结果，所以我不确定它在做什么。|1284187|entityMap^0|0|0|V|5|13|D|0|5|A|G|4|N|3|0|0|C|F|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@$I|12|J|13|K|L]|$I|14|J|15|K|L]|$I|16|J|17|K|L]]|9|@]|A|$]]|$1|O|3|P|5|D|7|18|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|19|8|@$I|1A|J|1B|K|L]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$]]

I believe the general solution is to use:

<pre><code>git rev-list -n1 --first-parent --until=&lt;a date string&gt; &lt;a ref&gt;
</code></pre>

Without --first-parent, you might get a commit from a branch that was later merged into <code>a ref</code> but hadn't been merged as of <code>a date string</code>. 

Here's an alternative using <code>--children</code> and <code>grep</code> instead of <code>-n1</code>:

<pre><code>mlm_git_ref_as_of() {
 # # Examples #
 #
 # Show all commits between two dates:
 #
 # git log $(mlm_git_ref_as_of '2012-05-21 09:00:00-0400')..$(mlm_git_ref_as_of '2012-05-21 17:00:00-0400')
 #
 # Show diffs of all commits between two dates:
 #
 # git diff $(mlm_git_ref_as_of '2012-05-21 09:00:00-0400')..$(mlm_git_ref_as_of '2012-05-21 17:00:00-0400')
 local as_of="$1"
 local ref="${2:-HEAD}"
 # Get the most recent commit (--children, grep -v ' ') that was on
 # the given branch ($ref, --first-parent) as of a given date
 # ($as_of)
 git rev-list --children --first-parent --until="$as_of" "$ref" | grep -v ' '
}
</code></pre>

I wasn't familiar with <code>git whatchanged</code> before reading this Q&amp;A, but it gives very different results for me, so I'm not sure what it's doing.

blocks|key|1284199|text|git+diff+--stat+@{2013-11-01}..@{2013-11-30}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1284200|或|unstyled|1284201|git+diff+--stat+@{2.weeks.ago}..@{last.week}|1284202|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|I|3|-4|5|F|7|N|8|@]|9|@]|A|$]]]|J|$]]

<pre><code>git diff --stat @{2013-11-01}..@{2013-11-30}
</code></pre>

or

<pre><code>git diff --stat @{2.weeks.ago}..@{last.week}
</code></pre>

blocks|key|1284228|text|我将采用我的方法:日期的git+log为您提供了当前分支的提交散列。然后我只使用像git+diff+8fgdfg8..565k4l5这样的东西，它让我根据文件聚合得到适当的差异。希望这能有所帮助，虽然没有经过太多测试|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1284229|entityMap^0|C|7|15|P|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I'll throw in the way I do it: 
<code>git log</code> for a date gives you commit hashes for the current branch. Then I just use something like <code>git diff 8fgdfg8..565k4l5</code> which gives me proper difference aggregated by files. Hope this helps, not tested much though

Or just all the commits that occurred between two dates? In SVN, you could do something like 

<pre><code>svn diff -r{date}:{date}
</code></pre>

to do it! I can't seem to find a Git equivalent to this.

Specifically I'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?

或者只是发生在两个日期之间的所有提交？在SVN中，您可以这样做svn diff -r{date}:{date}去做吧！我似乎找不到与此相当的Git。具体地说，我正在考虑编写一个脚本，以便每天发送电子邮件，其中包含当天提交的所有代码以及提交人。

问如何使用Git获取两个日期之间发生的所有提交之间的差异？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Git获取两个日期之间发生的所有提交之间的差异？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Git获取两个日期之间发生的所有提交之间的差异？
EN