cvs2hg emit .hgeol?
Martin Geisler
mg at lazybytes.net
Wed Aug 24 15:33:14 UTC 2011
Tom Udale <tom at ionoptix.com> writes:
> Indeed this synthetic add is exactly the goal. It does address the
> issue you mention (and which Martin confirmed for eol), namely that if
> you simply add .hgeol (or .hgignore for that matter) to a converted
> repository, you are ok going into the future, but you are hosed the
> moment you check out before the conversion time.
Well, since the history is already written, you're not really "hosed".
The only problem you could get, is if you update back to an old
revision, add a file with the wrong newline format and then commit it.
To me, that sounds like a rare problem. If you encounter it, then just
copy in a good .hgeol file and fix the offending files with a new
commit.
There is more value in having a good .hgignore file in all changesets so
that your build products wont show up in 'hg status' when you update
back and build an old release.
--
Martin Geisler
Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20110824/e0fc6d80/attachment.asc>
More information about the Mercurial
mailing list