Relative path operations in bzr?

[Andrew S. Townley]

Hi folks,

I quickly scanned the archives and didn't see anything like my question
there, but I'm trying to pick a new, distributed VCS and giving bzr a
try on a new project I'm working on.  I was a bit surprised (based on
many (10+)) years of working with CVS when running the bzr commands (bzr
status, for example) in any directory of the repository produced the
same results.

I was a bit annoyed when out of habit, doing an unqualified bzr commit
-m "my massive change" in a deep subdirectory where I had a bunch of
pending changes actually committed things that weren't yet checked in in
the rest of the repository.

The simple question is:  is this the intention of how it is supposed to
work?

I don't have a bunch of bandwidth at the moment, or I'd try and dust off
my python skills and have a go at seeing why this happens.  It seems a
bit non-intuitive to me, but maybe that's just the conditioning from
CVS. :)

Any comments/feedback appreciated.

Cheers,

ast

***************************************************************************************************
The information in this email is confidential and may be legally privileged.  Access to this email by anyone other than the intended addressee is unauthorized.  If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful.  If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
***************************************************************************************************