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

Re: Maintaining historical data in a git repo

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 30, 2012, 16:52 UTC
Message-ID
<7vehsam3pn.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CA+P+rLcWT0SZQjW2LtFXXCDRwjMp8daJ2hVup=7cnsRGbKw7xw@mail.gmail.com>
Yuval Adam <yuv.adm@gmail.com> writes:
> Is this something that is definitively complicated with git?

That's not really "is it complicated with git" question, I would have to say. Any version control system you would build history starting from one point going _forward_, never inserting past event as you dig back.

Surely, you could fake it by rewriting history, but I do not think SCM is particularly geared towards such a use case *while* investigating the history of the law and recording your findings.

I do agree that once such a discovered history is *complete*, it would be nice to record it in a SCM with a powerful history digging capability in chronological order, though.

Previous: Jakub NarebskiNext: Yuval Adam
Message 6 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.