> Is there a long term plan to fold the EDBDIC changes into the main
> line, though? Or is that unlikely-to-impossible?
My goal would be for as much of the port as you would accept to be folded
into the main line. Hopefully once the port lands in the repository people
can give us ideas on how to handle the porting issues to make them more
"palatable". For example, a big issue, and significant amount of the code
changes in the port, is the hex-escaping of string literals. I believe
that brane's idea would be for us to do the escaping in some kind of
pre-processor step during the build system. That would eliminate, or
greatly reduce, a significant amount of line of code changed. I am not
exactly sure how we would do it, but it will be worth the effort to explore
it.
As I have said before, our main goal at the moment is getting 1.1.x working
and released into the OS/400 community. We have svnserve completed and are
nearing the finish line with mod_dav_svn. Once that is done, we can turn
our attention to synching the port with trunk as well as looking for more
elegant ways to tackle the issues.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Feb 27 21:37:29 2005