In fact, I am locally using git to keep the history of my LDRAW files (and models and scenes).
I have a git repository containing the initial parts release,
and then have applied each parts update one after another.
The repository reflects the whole lifecycle of a file.
When a new parts update comes out, I apply it and commit it as a "change" to all the affected *.dat and other files.
I do the same for unofficial files coming from the PT,
and my models, and my scenes composed of models.
I also would LOVE to see a revision controlled PT DAT files server
(we could even use github etc.), but the problem is that then the review etc. mechanisms will not be available,
and in fact a new PT would have to be written.
Question is if it would be worth the effort.
In an ideal setup, I would like to be able to submit part updates to the PT via a git push
instead of a parts upload via web interface.
- just my personal opinion
Steffen
I have a git repository containing the initial parts release,
and then have applied each parts update one after another.
The repository reflects the whole lifecycle of a file.
When a new parts update comes out, I apply it and commit it as a "change" to all the affected *.dat and other files.
I do the same for unofficial files coming from the PT,
and my models, and my scenes composed of models.
I also would LOVE to see a revision controlled PT DAT files server
(we could even use github etc.), but the problem is that then the review etc. mechanisms will not be available,
and in fact a new PT would have to be written.
Question is if it would be worth the effort.
In an ideal setup, I would like to be able to submit part updates to the PT via a git push
instead of a parts upload via web interface.
- just my personal opinion
Steffen