> Knowing what not to put in is sometimes the best way to keep good code.
What does that have to do with exposing a read only versioned history? Nobody is asking him to give the whole world commit privileges.
What does that have to do with exposing a read only versioned history? Nobody is asking him to give the whole world commit privileges.
ftp://ftp.porcupine.org/mirrors/postfix-release/index.html
It's tarballs for each release, with associated patches for each release. That's a pretty complete read only versioned history.
Why does it have to be a VCS?
And because they already have a VCS, and are just stubbornly unwilling to share all that useful information with the wider community.
I get that this clashes with the culture you're used to working in, but I don't see where it's actually impactful in a real world sense.
edit: a slight rewording
Giving Weitse the benefit of the doubt, his commit logs are probably very useful indeed, and not sharing them makes the codebase that much less useful to everyone else.
Edit to add: the canonical example is bisection. When something breaks, it is awesome to bisect it down to the precise change that broke it. Bisection lets you narrow the scope down to a vastly smaller problem space than a whole release would.