Re:Fork Your Application's Data (Not Just Your Code)
by TheMakeA on Thursday November 08, 2012 @02:37PM
(#4759453)
Interesting. I would take it a step further and say that everything related to your project should be forkable and branchable. Your source, your assets, your databases, etc. I would love to be able to go back to any moment in the projects history and get a full, working build.
[ Parent
| on HN ]
Re:Fork Your Application's Data (Not Just Your Code)
by Q6T46nT668w6i3m on Thursday November 08, 2012 @03:11PM
(#4759595)
I would take it a step further and say that everything related to your project should be forkable and branchable. Your source, your assets, your databases, etc.
Isn’t that the advantage of Perforce?
Re:Fork Your Application's Data (Not Just Your Code)
by TheMakeA on Thursday November 08, 2012 @03:14PM
(#4759609)
It is possible with Perforce, but it is far from ideal. Compare branching in Git to branching in Perforce. There's still a lot of room for improvement.
Re:Fork Your Application's Data (Not Just Your Code)
by hythloday on Thursday November 08, 2012 @07:31PM
(#4760664)
You should compare branching in Git to "streaming" in Perforce:
http://www.perforce.com/product/product_features/perforce_st...