- From: Peter Linss <peter.linss@hp.com>
- Date: Wed, 16 Oct 2013 11:59:25 -0700
- To: Rebecca Hauck <rhauck@adobe.com>
- Cc: "public-test-infra@w3.org" <public-test-infra@w3.org>
Received on Wednesday, 16 October 2013 18:59:49 UTC
On Oct 16, 2013, at 10:39 AM, Rebecca Hauck <rhauck@adobe.com> wrote: > Hey Peter, > > I just updated our github instructions with info about the testharness (resources) subrepo [1]. Rather than writing up separate instructions for CSS test writers, can we just add it as subrepo as Tobie suggested in the PR comments? > > Will that interfere with the other repo changes you're making? Again, I'm concerned about the timing here because I'd like to have the repos and the docs all in place for the event -- preferably well before as we're encouraging registrants to get set up prior to that day. > > Thanks! > -Rebecca > > [1] https://github.com/w3c/testtwf-website/pull/162 Let me do some tests with hg-git to see how it reacts to submodules. It's also not clear to me if we'd want that mirrored on the mercurial side as a subrepo. I don't know that much about how git handles submodules, but in hg a subrepo would stay fixed at a particular revision unless the parent is updated to use a new revision. In other words, we wouldn't get the automatic updating of the resources directory, as we do know by leaving them separate. Is this what's really wanted? I haven't seen any discussion about making the resources directory a submodule in the main WPT repo, so I'm not sure what the goals of this change are. Peter
Received on Wednesday, 16 October 2013 18:59:49 UTC