[issue1630] Don't clobber existing bundle with incoming --bundle by default

[Matt Van Gundy]

New submission from Matt Van Gundy <matt-mercurial at shekinahstudios.com>:

I was just trying to view which changesets were in a bundle I had been given.  I 
hg help incoming showed me that there was a --bundle option.  Stupidly, without 
reading the rest of the help, I run hg incoming --bundle mybundlefile and it 
proceeds to clobber the only copy of the bundle I had.

It would be helpful if options like --bundle (and others that create new files 
where the file wouldn't be expected to exist) would give an error if the file 
existed unless an option like --force or --clobber was specified.

Thanks!

----------
messages: 9187
nosy: mattvg
priority: feature
status: unread
title: Don't clobber existing bundle with incoming --bundle by default

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1630>
____________________________________________________