Comments on: Bazaar: Moving files after the fact http://muffinresearch.co.uk/archives/2009/01/29/bazaar-moving-files-after-the-fact/ the personal blog of Stuart Colville covering modern web development techniques and best practices Mon, 21 May 2012 05:48:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Sina Salek http://muffinresearch.co.uk/archives/2009/01/29/bazaar-moving-files-after-the-fact/comment-page-1/#comment-65504 Sina Salek Mon, 25 Jan 2010 13:24:59 +0000 http://muffinresearch.co.uk/?p=460#comment-65504 It's possible and actually not very difficult. they may implement it in future versions. you might want to fill a feature request ;) It’s possible and actually not very difficult. they may implement it in future versions. you might want to fill a feature request ;)

]]> By: Stuart Colville http://muffinresearch.co.uk/archives/2009/01/29/bazaar-moving-files-after-the-fact/comment-page-1/#comment-64889 Stuart Colville Thu, 29 Jan 2009 22:38:56 +0000 http://muffinresearch.co.uk/?p=460#comment-64889 @Karl: Technically I can't see why not. But, on a practical level I think keeping things like this as explicit is better than requiring an interface to resolve ambiguity. @Karl: Technically I can’t see why not. But, on a practical level I think keeping things like this as explicit is better than requiring an interface to resolve ambiguity.

]]> By: Karl Fogel http://muffinresearch.co.uk/archives/2009/01/29/bazaar-moving-files-after-the-fact/comment-page-1/#comment-64888 Karl Fogel Thu, 29 Jan 2009 17:32:49 +0000 http://muffinresearch.co.uk/?p=460#comment-64888 You know, though... I wonder if the --after flag is even necessary? Is there any reason plain 'bzr mv' can't just Do The Right Thing if it detects that the file has already been moved? In cases where the content of bar is the same as the recorded versioned content for foo, it's trivial. But even when bar differs, it's usually going to be recognizably similar. And bzr could simply error (and recommend --after or --force or something) if the relationship is not automatically detectable. You know, though… I wonder if the –after flag is even necessary? Is there any reason plain ‘bzr mv’ can’t just Do The Right Thing if it detects that the file has already been moved?

In cases where the content of bar is the same as the recorded versioned content for foo, it’s trivial. But even when bar differs, it’s usually going to be recognizably similar. And bzr could simply error (and recommend –after or –force or something) if the relationship is not automatically detectable.

]]>