bzr 0.0.3 released

[David Allouche]

On Thu, 2005-04-07 at 21:37 +1000, Martin Pool wrote:
> On Thu, 2005-04-07 at 12:58 +0200, Markus F.X.J. Oberhumer wrote:
> > And somewhat related to mv, I think that automatically removing files
> > from the repo is a really bad idea. Think of "vi a", "mv b c", "bzr
> > commit". "mv b c" should have been "bzr mv", but now b has silently been
> > removed without any warning. No file should get added without "bzr add",
> > and none removed without "bzr remove".
> 
> Only 'no warning' if you commit without checking the status or diff,
> which I suppose people do sometimes do.
> 
> So you'd rather have an error if you tried to commit when some files had
> been removed?

That's how it works in Arch, when you use explicit ids. File additions,
deletions and renames done at the filesystem level without notifying the
VCS will cause errors.

It works differently for directories, since they always contain their
own explicit ids. And there are some cases that will not be caught, like
swapping two files without telling the VCS.

There have been a little bit of flame regarding inventory methods, those
unhappy generally advocate the exclusive use of explicit ids, for
reasons of least surprise. The irregularities introduced by the the
tagline tagging method are deemed not to be worth the added convenience.

In a nutshell, it seems that people do not mind having to tell the VCS
about additions, renames and deletions. But they do mind having to tell
it _sometimes_.

-- 
                                                            -- ddaa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050407/c4f6a345/attachment.pgp