Yes. But why not creating new CVS branches for each stable release ?
It allows us to do "hard" changes in the CVS tree, like renaming directories and convert a file into a directory (consider .pmod).
/ Martin Nilsson (räfsfiskal)
Previous text:
2004-05-05 01:36: Subject: Re: CVS is broken
Hi,
Sure, but what would the point be? It's no problem to remove the old development repository once it becomes the stable release and then fork a new development branch. It's just the way Pike has choosen to do things.
Yes, would be a good thing.
It is better to document this policy instead of inventing bad fixes. I think David was not aware of this practise and thus his conclusion that the repository was broken. If he had known that it's now called 7.7, he would have checked that out instead.
Yes. But why not creating new CVS branches for each stable release ?
/ David Gourdelier
/ Brevbäraren