From: Thomas Rast <trast@student.ethz.ch>
To: Kelly Dean <kellydeanch@yahoo.com>
Cc: <git@vger.kernel.org>
Subject: Re: Does content provenance matter?
Date: Mon, 7 May 2012 10:23:38 +0200 [thread overview]
Message-ID: <878vh4flh1.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <1336250956.54413.YahooMailClassic@web121505.mail.ne1.yahoo.com> (Kelly Dean's message of "Sat, 5 May 2012 13:49:16 -0700 (PDT)")
Kelly Dean <kellydeanch@yahoo.com> writes:
> [copying B/X over to C/X is not recorded as such], on the theory that
> just content, not provenance, is what matters.
> [merging branches *is* recorded], on the theory that not only content,
> but also provenance, matters.
> 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), the same as you're supposed to figure out renames at
> search time and figure out the movement of lines within/among files at
> search time (by looking at all files in the parent commit(s))?
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.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-05-07 8:23 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 [this message]
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
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=878vh4flh1.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--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).