From: Kelly Dean <kellydeanch@yahoo.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: Does content provenance matter?
Date: Mon, 7 May 2012 14:43:23 -0700 (PDT) [thread overview]
Message-ID: <1336427003.53220.YahooMailClassic@web121504.mail.ne1.yahoo.com> (raw)
In-Reply-To: <878vh4flh1.fsf@thomas.inf.ethz.ch>
--- On Mon, 5/7/12, Thomas Rast <trast@student.ethz.ch> wrote:
> What's the difference between the following series of
> commits?
>
> Foo
> Bar
> Revert Bar
>
> and
>
> Foo
>
> You claim that they're the same, because the tree state
> after each is
> the same. But I learned that Bar was broken, and
> recorded it for all to see.
No, I don't claim they're the same. Different commits have different timestamps (and different commit messages, but that's not useful for automatic searching to find which commits are derived from which others). Consider if "Revert Bar" and "Bar" didn't point to their parents; could you still deduce from them that Bar was broken? Yes--on the basis of the commit timestamps (which shows their temporal order) and the contents of the trees which the commits point to (which shows that Revert Bar undoes a change made in Bar).
next prev parent reply other threads:[~2012-05-07 21:43 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 [this message]
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
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=1336427003.53220.YahooMailClassic@web121504.mail.ne1.yahoo.com \
--to=kellydeanch@yahoo.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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).