On Wed, Jan 15, 2014 at 06:13:30AM -0500, Jeff King wrote:
On Wed, Jan 15, 2014 at 11:37:08AM +0100, David Kastrup wrote:
The question is what guarantees I have with regard to the commit date of
a commit in relation to that of its parent commits:
a) none
b) commitdate(child) =
Hi,
I am in the process of rewriting the core logic of git blame (the
current speed of which is quite an impediment to some workflows).
I currently have one question I don't see an answer to right away, and
that question arises in doing a reasonably robust traversal of commits
without
On Wed, Jan 15, 2014 at 11:37:08AM +0100, David Kastrup wrote:
The question is what guarantees I have with regard to the commit date of
a commit in relation to that of its parent commits:
a) none
b) commitdate(child) = commitdate(parent)
c) commitdate(child) commitdate(parent)
a) none
Jeff King p...@peff.net writes:
On Wed, Jan 15, 2014 at 11:37:08AM +0100, David Kastrup wrote:
The question is what guarantees I have with regard to the commit date of
a commit in relation to that of its parent commits:
a) none
b) commitdate(child) = commitdate(parent)
c)
Jeff King p...@peff.net writes:
There are some parts of the code that will behave badly with clock skew.
For example, --since will stop traversing when we hit a certain point.
It requires a fixed number of too old commits before quitting, though,
in an attempt to bypass small runs of skewed
On Wed, 15 Jan 2014 12:40:29 +, David Kastrup wrote:
...
With a single root, depth helps a lot. When looking for a common
parent of a number of commits, you first shorten all ancestries to the
same size and then you can look for the point of convergence in
lockstep.
Hmm, how about
Andreas Krey a.k...@gmx.de writes:
On Wed, 15 Jan 2014 12:40:29 +, David Kastrup wrote:
...
With a single root, depth helps a lot. When looking for a common
parent of a number of commits, you first shorten all ancestries to the
same size and then you can look for the point of
On Wed, 15 Jan 2014 14:00:30 +, David Kastrup wrote:
Andreas Krey a.k...@gmx.de writes:
...
Hmm, how about traversing from all the start commits downwards
simultaneously, noting which start you say each commit from, and stopping
when you have a commit carrying all start labels?
It
8 matches
Mail list logo
