> I believe this is fixed now:
>
> $ bzr --version
> Bazaar (bzr) 1.11dev
> from bzr checkout /home/kfogel/src/bzr/bzr.dev
> revision: 3828
> revid: <email address hidden>
> branch nick: bzr.dev
> Python interpreter: /usr/bin/X11/python 2.5.2
> Python standard library: /usr/lib/python2.5
> bzrlib: /home/kfogel/src/bzr/bzr.dev/bzrlib
> Bazaar configuration: /home/kfogel/.bazaar
> Bazaar log file: /home/kfogel/.bzr.log
>
> Copyright 2005, 2006, 2007, 2008 Canonical Ltd.
> http://bazaar-vcs.org/
>
> bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
> you may use, modify and redistribute it under the terms of the GNU
> General Public License version 2 or later.
>
> $ bzr info
> Standalone tree (format: pack-0.92)
> Location:
> branch root: .
>
> Related branches:
> parent branch: http://bazaar-vcs.org/bzr/bzr.dev/
> $ touch unversioned_file
There's a misunderstanding here, this is not the point of this bug report!!
This is about non existent files.
The problem is what happens if you do this:
/bin/rm -f BLAH BLAH_BLAH
bzr status -v -S BLAH BLAH_BLAH unversioned_file README TODO
Karl Fogel <email address hidden> writes:
> I believe this is fixed now: src/bzr/ bzr.dev src/bzr/ bzr.dev/ bzrlib .bazaar .bzr.log bazaar- vcs.org/ bazaar- vcs.org/ bzr/bzr. dev/
>
> $ bzr --version
> Bazaar (bzr) 1.11dev
> from bzr checkout /home/kfogel/
> revision: 3828
> revid: <email address hidden>
> branch nick: bzr.dev
> Python interpreter: /usr/bin/X11/python 2.5.2
> Python standard library: /usr/lib/python2.5
> bzrlib: /home/kfogel/
> Bazaar configuration: /home/kfogel/
> Bazaar log file: /home/kfogel/
>
> Copyright 2005, 2006, 2007, 2008 Canonical Ltd.
> http://
>
> bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
> you may use, modify and redistribute it under the terms of the GNU
> General Public License version 2 or later.
>
> $ bzr info
> Standalone tree (format: pack-0.92)
> Location:
> branch root: .
>
> Related branches:
> parent branch: http://
> $ touch unversioned_file
There's a misunderstanding here, this is not the point of this bug report!!
This is about non existent files.
The problem is what happens if you do this:
/bin/rm -f BLAH BLAH_BLAH
bzr status -v -S BLAH BLAH_BLAH unversioned_file README TODO