From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Consistency question
Date: Wed, 15 Jan 2014 11:37:08 +0100 [thread overview]
Message-ID: <8761pl8raj.fsf@fencepost.gnu.org> (raw)
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 determining topology first:
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)
Obviously, I can rely on c) being true "almost always": it's definitely
good for a heuristic used for improving performance (meaning as an
ordering criterion for a commit priority queue). The problem is how
much I should cater for graceful behavior for the cases where it's not.
Does git do any actual checks before pushing?
--
David Kastrup
next reply other threads:[~2014-01-15 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 10:37 David Kastrup [this message]
2014-01-15 11:13 ` Consistency question Jeff King
2014-01-15 11:40 ` David Kastrup
2014-01-15 12:44 ` Andreas Krey
2014-01-15 13:00 ` David Kastrup
2014-01-15 13:45 ` Andreas Krey
2014-01-15 11:55 ` David Kastrup
2014-01-18 1:22 ` Mike Hommey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761pl8raj.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.