When manually resolving directory conflicts isn't a feature

Talden talden at gmail.com
Mon Apr 6 06:15:37 BST 2009

On Mon, Apr 6, 2009 at 1:43 PM, Mary Gardiner <mary at puzzling.org> wrote:
> I wanted to raise this here rather than filing bugs as I have a suspicion
> they'd be marked invalid-that's-a-feature like bug 102001.

Agreed this is a bug, in that there's no convenient way of the tool
doing the right thing

> While I realise it's an important feature to never have Bazaar delete files
> that it doesn't know about, this workflow is really annoying. What should I do?

Having a '--strict' option for switch might be nice - it would protect
you from getting into this state (it should check local modifications
and unversioned content).

'clean-tree' from bzr-tools might be handy to be brought into core to
provide a convenient means of cleaning up quickly - though it would be
nice if a list of paths could be provided to focus the cleaning

NB: Subversion has an equally horrible way of dealing with this scenario.


More information about the bazaar mailing list