One Mercurial repository for spec and code?

With Mercurial you only ever clone the whole repository, unlike, say,
Subversion, where you can check out and work with a subdirectory.

If, as intended, we also put the spec into the Mercurial, then anybody who
wants to clone the repository to get the spec will also get the code, and
vice-versa, and they will get all updates to both parts whenever they
update.

If this becomes a problem, we could either ask the W3C support team for a
second repository or copy the current repository to GitHub, delete the
spec parts from that repository, and use GitHub as a Mercurial hub by
using the 'Hg-git' plugin for Mercurial.  Doubtless there are other
options, too.

Regards,


Tony.

Received on Saturday, 6 April 2013 20:39:21 UTC