On Tue, Dec 09, 2008 at 09:17:05PM +0100, Johannes Hofmann wrote:
Given the current patch-rate we could also easily stick with CVS for the main repository I think. It's just for the longer living css-prototype branch where I wanted something more comfortable than CVS.
So what will happen to non-css patches (*cough* HTTP auth *cough*)? Will they go into CVS or the dillo-main Mercurial repository? Didn't Jorge say something about committing only to Mercurial for a while? (Or did I misunderstand?) To be honest, why not migrate to Mercurial now? After all, CVS *is* obsolete and clunky, Mercurial *can* do the job, and some key Dillo developers are *already* maintaining and using Mercurial repositories of the Dillo source. It would also save me the trouble of layering git over CVS just to manage my local patches. Why not just do it? Regards, Jeremy Henty -- And so concludes the verse "Jabberwocky" by Lewis Carroll. A piece of nonsense verse embedded in a nonsense work, it resembles the "real world" about as much as a computer program does. Which is perhaps why Lewis Carroll is so popular among computer programmers. -- Craig A. Finseth.