W3C home > Mailing lists > Public > public-css-testsuite@w3.org > April 2012

Re: Submission of transform tests

From: Aryeh Gregor <ayg@aryeh.name>
Date: Mon, 16 Apr 2012 08:50:19 +0300
Message-ID: <CAKA+Ax=6Ay_to+hZAJiaeBxhNc7b9nVkag7+ip7eed2bHvM5vg@mail.gmail.com>
To: "Linss, Peter" <peter.linss@hp.com>
Cc: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
On Sun, Apr 15, 2012 at 10:42 PM, Linss, Peter <peter.linss@hp.com> wrote:
> Actually Shepherd worked as designed there. Shepherd tracks each asset by name, so if a file's name changes it's considered a new asset. It does understand that the same asset may be represented by multiple files (as commonly happens with support files, and sometimes with references and tests as they're being worked on) and it tracks each file independently, but they're all considered the same asset.
> I do have some improvements on how Shepherd handles file renames on my to do list (it's all still a work in progress). When comments are entered they are logged against a specific revision of a specific file, so I can have the comments follow the file in the case of renames.

In this specific case, when I checked in a new test that had the same
name as an existing one, Shepherd seemed to treat it as a new version
of the existing test, even though I didn't delete the existing test.
I suggest that in this, it's probably better for Shepherd to complain
loudly and ignore the new file rather than the old one as long as
there's a naming conflict.

(Does Shepherd have a bug tracker?  I don't see a component for it at
Received on Monday, 16 April 2012 05:51:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:24 UTC