[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Maintaining historical data in a git repo
From:       Yuval Adam <yuv.adm () gmail ! com>
Date:       2012-03-30 13:34:08
Message-ID: CA+P+rLeyEcZPudhLWavB74CiDAqpn+iNkk4F8=NK_yGaJPMmyA () mail ! gmail ! com
[Download RAW message or body]

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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]