3 ms·
No commit history? It would have been interesting to follow the development work to see what changes they've made compared to PostgreSQL.
by JoelJacobson 5y ago
No commit history? It would have been interesting to follow the development work to see what changes they've made compared to PostgreSQL.
- llaolleh 5y agoThey are following the Gaussian approach. Show only the final result!
- antoncohen 5y agoThis is effectively required when open sourcing something that was previously internal. I've done it at a company. There could be company internal things that leak in old revisions of code and commit messages. Even if the latest commit on master is clean, it is really hard to know that every revisions, throughout the whole history is clean.
- JoelJacobson 5y agoGood point. In such a case, I think it would still be nice if at least trying to split the total change into a few separate commits, that builds upon each other. That way the commit log could be a good start to look at for someone who wants to understand the code base.
- JoelJacobson 5y agoWith the first commit being the specific commit from the PostgreSQL repo which they base their work on, i.e. that they forked from.