5

I don't like Mercurial polluting the source tree with .orig files and such. Is it possible to keep all such files in /tmp, for example?

  • hg doesn't do that on any of the installs I've used - are you sure it's not another process – Pete Kirkham Oct 09 '09 at 09:21
  • There is even a stackoverflow thread about a similar issue: http://stackoverflow.com/questions/1067680/how-to-automatically-remove-all-orig-files-in-mercurial-working-tree –  Oct 09 '09 at 10:14
  • That's why I thought Mercurial does it. –  Oct 09 '09 at 10:15
  • Though I'm not doing a merge, so it may be a separate issue. –  Oct 09 '09 at 10:16

2 Answers2

3

The question to which you link: How to automatically remove all .orig files in Mercurial working tree? has an answer that suggests using an update hook to delete the files automatically, which you could very easily turn to a 'mv'. That would be automatic and easy.

Community
  • 1
  • 1
Ry4an Brase
  • 78,112
  • 7
  • 148
  • 169
0

I'm not sure that's mercurial doing that, it might just be your merge programs. If it's mercurial, I'm sure it's not currently configurable.

tonfa
  • 24,151
  • 2
  • 35
  • 41
  • 3
    The revert command makes `.orig` files unless you use `--no-backup`. – Martin Geisler Oct 10 '09 at 11:17
  • 2
    I believe the issue is Kdiff3 [bundled w tortoise Hg] (or maybe another merge tool) .. In kDiff3, If you look under SETTINGS > CONFIGURE kDiff3 > DIRECTORY... the last option is "backup file (.orig)" - If you uncheck this KD3 will not write the file - I don't think you "need" is as Hg is keeping a record 'pre merge' anyway - can someone else more experienced in distributed SC please weight in on this ... thx – j-p Sep 06 '11 at 04:03
  • @jpmyob: THANK YOU! Even after going with the --no-backup change, I was still seeing new .orig files being created. Updating kdiff3's setting is the additional step I was missing -- all is well now. – Mass Dot Net Mar 10 '15 at 16:10