Ok, xml-batik is now cleared for final migration:
http://issues.apache.org/jira/browse/INFRA-357

I expect Henri Yandell to complete the migration this week, after which
we will get notified and the CVS module is set to read-only.

On 23.06.2005 12:33:03 Cameron McCormack wrote:
> Jeremias Maerki:
> > I've cleared FOP for the final migration but I'm hesitant to do the same
> > for Batik. Cameron, what do you think? 
> 
> As long as that ConcreteInterpreter.java file goes away, it looks ok.  I
> tested the trunk without this file and it compiles and runs.  The svg12
> branch is ok too.
> 
> I also just compared all the files between the CVS and SVN checked out
> directories for the trunk and svg12 branches and everything is in order,
> apart from that ConcreteInterpreter.java file.
> 
> The only thing I'm puzzles about is the 'apache' branch.  I don't see it
> mentioned in the viewcvs web pages.  I don't know whether this is
> something that is deliberately in CVS or something that popped up by
> mistake in SVN?

Look here:
http://cvs.apache.org/viewcvs.cgi/xml-batik/sources/org/apache/batik/bridge/Bridge.java?only_with_tag=apache

Bridge.java, for example, contains a reference to a "vendor branch"
called "apache". Looking at the commit message it becomes clearer what
was happening there. I think it was a temporary branch for a Hackathon
happening back in 2000.

I'd simply remove that branch and any other branches or tags that are
not important. We have stuff like this in FOP, too. It is easily removed
but still not lost should anyone ask for it later. The benefits of a
good version control software. :-)


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to