Yuya Nishihara <[email protected]> writes: > Hi, > > Richard wrote: >> What I'm seeing is that when I pull my subversion tree, Mercurial >> marks everything as "modified" even when I haven't done anything to >> the files. >> >> On closer inspection it seems to be an EOL convention issue. All the >> files marked as modified have had their EOL bytes changed in my local >> repository. > > I'm not sure, but possibly: > 1. Mercurial (hgsubversion) converts 'SVN changesets' to hg at repo level, > where no eol conversion exists. > 2. hgsubversion calls 'SVN update' to prepare working copy?, where eols > are converted. > 3. Then, there's difference between working copy and repo. > > You'll get more precise answer at > http://groups.google.com/group/hgsubversion/ > >> Mercurial seems to have some sort of other weird policy that I can't >> figure out.
Our policy is simple: we don't mess with your data by default. > AFAIK, Mercurial does nothing about EOL, unless you enables hg-eol > extension. It is called the 'eol' extension and you can read about it here: http://mercurial.selenic.com/wiki/EolExtension -- Martin Geisler Mercurial links: http://mercurial.ch/
pgpOj0NXQG8Pu.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
