On Fri, Mar 30, 2012 at 6:10 PM, Seth Robertson <in-gitvger@xxxxxxxx> wrote: > > Revision control shouldn't be used to change the past (even if git > allows this with sufficient amounts of pain/warning to all users). > What it is extremely good at is preserving the past and tracking the > changes that are made. This is exactly what we _do_ want to do. Our use case for this is like so: "ok, this is how the law is today, and we're not quite sure how it got to this point" But then some X time later: "so we found out that clauses (1), (e) and (X) were changed on March 30, 1957, and we want to know this for future reference" So, yes, we do need a way of knowing (blaming?) what happened in the past and how the law was shaped over time. Is this something that is definitively complicated with git? -- Yuval Adam http://y3xz.com -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html