At 05:32 PM 11/23/2002, Roy T. Fielding wrote: >>Since we renamed the repository to httpd from httpd-2.0 (there is >>a symlink for now), the CVSROOT/avail file doesn't match >>the repository name, and therefore I can't commit. Can we >>fix that so I can commit to the new "httpd" repository directly? > >Why the heck was that done? Too many things get screwed over >when you change a module name in cvs. > >-1 -- I am reverting that change to cvs. Don't screw with this stuff >without a clear plan in STATUS, and notify apmail and cvsadmin before >screwing with the filesystem. It would have been far more sensible >not to branch 2.0 and instead create a new module that doesn't suffer >from legacy versions.
Speaking of plans and the comments above, it seems to make sense to keep the httpd-2.0 CVS module name, until we are ready to release 2.0. All of the development effort is twords some future 2.2 or the current 2.0, and those that like to live on the bleeding edge check out cvs HEAD anyways. But we've been operating this was for months, with files that the respective RM's have chosen not to put into the current version, for whatever conservative and reasoned reasons. When 2.2 is 'cooked', I agree with Roy's observation, we toast the httpd repository (with complete history) in either CVS or SVN, based on the best-of-breed at that moment. Bill
