Why did you change the post title? This is not a “culture”, “git”, and “programming” article about “Help Stamp Out CVS In Your Lifetime”, this is ESR trying to find parts to build a computer which doesn’t really seem interesting at all.
It’s the latest instalment; there’s a fascinating back-history of threads discussing the issues ESRs been having, how he’s optimised the reposurgeon software, why he decided upon upgrading his hardware, and how that’s proceeding. Plus, of course, an option to donate to the cause.
I’d figured all of that was obvious. Clearly it wasn’t; what should I have done? Posted a link to the first (now irrelevant) thread in the series? Or created a separate aggregator page and linked to that? Serious question.
I would have probably linked to the first part of the series that is most relevant to “Help Stamp Out CVS In Your Lifetime” and then included links to the other parts in the story text box to explain it’s a multi-part series.
Yes, that would have been good to put in the story text or at the least as a comment after submitting the story. I was too lazy to hunt around esr’s site to find the other parts of the story.
Hopefully that’ll make for interesting reading, and better explain my choice of heading and use of the culture, git and programming tags. This series has a little of everything: humour, technical nitty-gritty, design philosophy, hardware and software history, free software culture …
Wait, really? If http://www.openbsd.org/cvsync.html is accurate, then a machine with 100x the memory of the largest repo is under three bucks an hour on EC2 (r3.8xl, $2.80/hr). What sort of a conversion process is it?
Why did you change the post title? This is not a “culture”, “git”, and “programming” article about “Help Stamp Out CVS In Your Lifetime”, this is ESR trying to find parts to build a computer which doesn’t really seem interesting at all.
It’s the latest instalment; there’s a fascinating back-history of threads discussing the issues ESRs been having, how he’s optimised the reposurgeon software, why he decided upon upgrading his hardware, and how that’s proceeding. Plus, of course, an option to donate to the cause.
I’d figured all of that was obvious. Clearly it wasn’t; what should I have done? Posted a link to the first (now irrelevant) thread in the series? Or created a separate aggregator page and linked to that? Serious question.
I would have probably linked to the first part of the series that is most relevant to “Help Stamp Out CVS In Your Lifetime” and then included links to the other parts in the story text box to explain it’s a multi-part series.
Right, that makes sense. So, sort of like what I put here, but posted along with the link? And possibly a bit more context?
Yes, that would have been good to put in the story text or at the least as a comment after submitting the story. I was too lazy to hunt around esr’s site to find the other parts of the story.
For those interested in the full history, in chronological order:
Hopefully that’ll make for interesting reading, and better explain my choice of heading and use of the culture, git and programming tags. This series has a little of everything: humour, technical nitty-gritty, design philosophy, hardware and software history, free software culture …
I wonder just what ESR intends to do after he converts all the CVS repos he can find. Is he going to force upload them and make the project use git?
Sure, I mean the only reason OpenBSD is still using CVS is because we couldn’t find anyone with enough RAM to convert our tree to git.
Wait, really? If http://www.openbsd.org/cvsync.html is accurate, then a machine with 100x the memory of the largest repo is under three bucks an hour on EC2 (r3.8xl, $2.80/hr). What sort of a conversion process is it?
No, not really.