[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Initial commit for EBCDIC Port

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-03-03 22:14:07 CET

I have been given commit access for the EBCDIC port. Before I set things
up and do our initial code dump, I wanted to be sure I am clear on what we
have decided for a structure.

I believe we settled on:


I wouldn't create "trunk" until we are ready to port to trunk.

Also do you have any guidelines/opinion on the initial code dump? Do you
want us to do it in one commit, or somehow try to break it into logical
chunks? I was thinking we ought to reserve the latter for when we start
trying to port this over to trunk. Ultimately the /branches/ebcdic/1.1.x
line is going to be a throwaway.

If we do one big code dump, do we need a detailed log message describing
every change to every file? We have changed almost every file in the main
libraries in some manner. I guess my preference would be to just do an
initial code dump with a minimal log message and then start to do things
the right way after that. Especially when we start working in

Finally, we are getting real close to the finish line on getting
mod_dav_svn working. I probably will not do the initial code dump until
we get a little further. I know that you didn't want to see a bunch of
commits as we are working these issues out, so it would just keep things



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 Thu Mar 3 22:15:50 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.