We do this in EpiDoc using an svn:external that pulls the latest tagged
copy in from its github repo. So there isn't actually a copy in the repo,
but when you check it out or update, you get one.
On Fri, Jan 30, 2015 at 8:42 AM, James Cummings
With regard to the Stylesheets that were there... there is a possible argument for having a local to TEI SVN copy of the Stylesheets. We use them for Guidelines production and of course just use the version on github. But we could take a copy of this at each of its releases and use that for the next release not then suddenly having surprises appear as changes continue to be made. So TEI Guidelines production as a consumer of the TEI Stylesheets not in a change-by-change kind of way but at stable releases.
Just throwing out the idea as food for thought.
-James
On 30/01/15 13:30, Martin Holmes wrote:
Since I was the one who originally proposed /obsolete/, IIRC, I'll respectfully retire.
But I have in the past spent an awful lot of time checking out various revisions of huge repos in an attempt to find something that got deleted without proper record-keeping, so please, if you do delete something, submit a detailed commit message saying what it was, what it was called, and why it's being deleted. "Cleaned up cruft" isn't helpful when you're trying to find something that you vaguely remember was an XSLT file that did something interesting with respStmts.
Cheers, Martin
On 15-01-30 05:19 AM, Majewski Stefan wrote:
I am with Hugh and Peter here.
Am 30.01.2015 13:27, schrieb Syd Bauman:
I think deletion is better than bothering with the "simply move obsolete/ directory" option. HOWEVER, far better than either of these is to *annotate* the old stuff.
The one reason against deletion is, that it becomes a bit difficult to find deleted stuff in SVN. One way to make this easier would be to have a HISTORICAL_README with the deletions documented or, which I would prefer, a tag in the commit message saying "DELETE filename" (or maybe repopath). Then it is quite easy to spot deletions without having to svn diff.
Deletion also has the benefit that the stuff that has been deleted is, when going back to the revision where it has still been present, in the context where it has been used (which is obviously important to properly understand the deleted artefact)
kind regards, Stefan
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived