From: Jakub Narebski <jnareb@gmail.com>
To: Kelly Dean <kellydeanch@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: Does content provenance matter?
Date: Mon, 07 May 2012 16:12:59 -0700 (PDT) [thread overview]
Message-ID: <m3397ba8lh.fsf@localhost.localdomain> (raw)
In-Reply-To: <1336250956.54413.YahooMailClassic@web121505.mail.ne1.yahoo.com>
Kelly Dean <kellydeanch@yahoo.com> writes:
> The basic question is, if provenance doesn't matter, then why does a
> git commit record its parent(s)? Why not omit this information, and
> figure it out at search time (by looking at all commits with older
> timestamps),
Because it is not possible to do in reliable way in face of parallel
concurrent branchy development by multiple developers... some of which
can have badly set clock.
Also, multiple merges of the same branch.
--
Jakub Narebski
prev parent reply other threads:[~2012-05-07 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 20:49 Does content provenance matter? Kelly Dean
2012-05-07 8:23 ` Thomas Rast
2012-05-07 21:43 ` Kelly Dean
2012-05-07 22:14 ` PJ Weisberg
2012-05-07 23:13 ` Kelly Dean
2012-05-08 0:03 ` Andrew Ardill
2012-05-08 9:23 ` Philip Oakley
2012-05-08 0:08 ` Junio C Hamano
2012-05-08 0:11 ` Junio C Hamano
2012-05-07 23:12 ` Jakub Narebski [this message]
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=m3397ba8lh.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=kellydeanch@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).