git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Maintaining historical data in a git repo

From
Yuval Adam <yuv.adm@gmail.com>
Date
Mar 30, 2012, 15:55 UTC
Message-ID
<CA+P+rLcWT0SZQjW2LtFXXCDRwjMp8daJ2hVup=7cnsRGbKw7xw@mail.gmail.com>
In-Reply-To
<201203301510.q2UFAqn6003864@no.baka.org>
On Fri, Mar 30, 2012 at 6:10 PM, Seth Robertson <in-gitvger@baka.org> wrote:
Show 5 quoted lines
>
> 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
Previous: Seth RobertsonNext: Seth Robertson
Message 3 of 13 in “Maintaining historical data in a git repo”
  1. Yuval AdamMar 30, 2012
  2. Seth RobertsonMar 30, 2012
  3. Yuval AdamMar 30, 2012
  4. Seth RobertsonMar 30, 2012
  5. Jakub NarebskiMar 30, 2012
  6. Junio C HamanoMar 30, 2012
  7. Yuval AdamMar 30, 2012
  8. david@lang.hmMar 30, 2012
  9. Mark LodatoMar 31, 2012
  10. Holding, LawrenceApr 1, 2012
  11. Ævar Arnfjörð BjarmasonApr 2, 2012
  12. Markus ElfringApr 3, 2012
  13. Andreas StrickerApr 3, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.