bzr send doesn't warn of file overwrite

Bug #272662 reported by William Fagan
0
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Wishlist
Unassigned

Bug Description

If you are using bzr send with the -o option to select a output file, bzr won't warn if the command will overwrite a previous file.

Revision history for this message
John A Meinel (jameinel) wrote :

So... we could warn but still continue, but at that point you've already overwritten the file. My personal preference would be a flag, like "rm -i" so you would explicitly ask to not overwrite files.

How would you see the UI for this?

Changed in bzr:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
William Fagan (libwilliam-deactivatedaccount) wrote :

I'm thinking send could stick with the --force option like a few of the other commands.

I know with the remove command it will strictly not remove a file if it isn't safe unless you do the --force options.
Or you could always ask for a Y or N response when something tries. I'm not sure if this it is something the bzr UI usually does any where else because I can not think of an example.

Martin Pool (mbp)
Changed in bzr:
status: Triaged → Confirmed
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.