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

Re: Maintaining historical data in a git repo

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Apr 2, 2012, 11:38 UTC
Message-ID
<CACBZZX46d8rx4ueY3-mNHfZ7T-zrw8rKsRG7VAoGZSbYEvOpiw@mail.gmail.com>
In-Reply-To
<CA+P+rLeDFu4KgEZPw=k67iMWVVGcZ3q48VZjgXNLXn3NdyQnow@mail.gmail.com>
On Fri, Mar 30, 2012 at 22:39, Yuval Adam <yuv.adm@gmail.com> wrote:
Show 5 quoted lines
> However, we perceive git as a very powerful tool, that can fit
> beautifully with the way legislation works today.
> The challenge for us - should we choose to accept it ;) - is to build
> a set of wrapper tools that allow us to use git in such a way, while
> enabling us to build up past history.

You can always solve this by having two repositories, you have one canonical Git repository with your laws using some text-based format to describe when each change was added.

You'd never rewrite the history of this repository since it would represent the history of your project to give a commit timeline to the law, and not attempt to make your commit log reflect changes in the law.

You could then have tools to export another Git history from that original repository, that one would be constantly rewritten and nobody would base changes on that.

You could also make the two one and the same, but you don't have to.
Previous: Holding, LawrenceNext: Markus Elfring
Message 11 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.