Dirk wrote:
Hello Aleksey,
just a dump question. Isn't this solved in the last nightly build with
the "out of memory" path? This patch will copy the files verbatim into
the dumpfile. So there shouldn't be a conversion involved. Or is
should the dumpfile have only LF terminators, even if the host
encoding is CR/LF?
Best regards
Dirk
Toby Johnson schrieb:
Aleksey Nogin wrote:
If I use the vss2svn (latest HEAD version) with the --auto_props
option and the auto-props file sets svn:eol-style=native one some of
the files, the files would not be converted correctly. The problem
here is that the dump file is _required_ to only have the LF line
terminators on files marked with svn:eol-style=native (see
http://svn.haxx.se/dev/archive-2006-07/0981.shtml ), but vss2svn
does not make any attempt to do that...
Should I file an issue report on this?
Aleksey
(Replying to Dirk's reply above...) I don't think that the problem is
"solved" by the out-of-memory patch. The problem as I understand it is
that any file which has the svn:eol-style=native is *required* to have
only LF terminators in the dumpfile. Of course most source files in the
typical VSS repo will have CR+LF terminators, so regardless of how we
actually copy the contents into the dumpfile, it will need to be
converted in order to produce a valid dumpfile.
I wonder if File::Copy allows some sort of "hook" so that we can process
each "chunk" on the fly to do this conversion? Otherwise it may be
necessary to create an intermediate file in order to perform the
conversion prior to the final copy to the dumpfile...
toby
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
