3 ms·
Again, none of that is precluded by a read-only public VCS. The process of discussing changes and patches on the mailing list can still be identical if that's w
by ef4 12y ago
Again, none of that is precluded by a read-only public VCS. The process of discussing changes and patches on the mailing list can still be identical if that's what they like.
People seem to be equating "expose some VCS" with "run a github-style repo where anybody can stick pull requests into your queue". The two are not the same.
It is entirely reasonable to ask an open source project to stop hiding useful information that they already have and could share at zero cost.
- quesera 12y agoI disagree about the usefulness of seeing code in progress. The inter-release diffs aren't very large, typically. I read them all, carefully. Why would Wietse want to have a public conversation about unfinished work? He's not looking for help.
- ef4 12y ago>The inter-release diffs aren't very large, typically. But they're much bigger than the individual commits, and so if something breaks in release X, I can ponder the whole diff or I can bisect the history and ponder a handful of lines.