On Fri, 30 Mar 2012, Yuval Adam wrote:
On Fri, Mar 30, 2012 at 7:52 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
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.
That is true.
It is very clear to us that an SCM is optimized for the prevalent use
case, which is tracking code (well, mostly code) as it is written.
Naturally this always starts at some point in time and progresses into
the future.
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.
Yes, this is not the usual use case, but we're highly motivated on
making this work.
We believe this could also be an interesting experience for the git
community in seeing how the git plumbing can be used for other cases,
even if they veer off on some weird tangent.
We'll definitely be back with more questions and updates, as we progress.
Thanks, everyone, for your responses and feedback!
you may want to take a hint from how the linux repository works.
When git was created, the as-of-then current version was commited as the
base and development went on from there.
Later on the linux historical repository was created (and re-created over
time as other versions were found).
The git graft command can be used to join the 'current' repository to the
'historical' repository so that they can be treated as one.
I strongly suspect that something along these lines is what you are
needing.
David Lang