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

Maintaining historical data in a git repo

From
Yuval Adam <yuv.adm@gmail.com>
Date
Mar 30, 2012, 13:34 UTC
Message-ID
<CA+P+rLeyEcZPudhLWavB74CiDAqpn+iNkk4F8=NK_yGaJPMmyA@mail.gmail.com>

As part of a public project to open-source the Israeli law code, we are looking into ways of represent such data in a git repository.

The main challenge is to represent historical data _in a semantically correct way_ within a git repository, while having the ability to change data that has occurred in the past. For example, we might have revisions B and C of a certain legal document, commit to repo, and at a later time want to add revision A to the proper place in the git commit tree (probably with rebasing or replacing). Allowing decentralization and updates is a major requirement.

We're trying to map out the various pros and cons of the different options of maintaining such a repo. Has anyone ever attempted something like this? Are there any projects that build on the git plumbing which provide wrapper APIs to handle historic data?

We really could use any reference or advice we can get on this subject.
Thanks,

-- Yuval Adam http://y3xz.com

Next: Seth Robertson
Message 1 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.