Relative path operations in bzr?

[Martin Pool]

On 19/09/05, Andrew S. Townley <andrew.townley at bearingpoint.com> wrote:

> 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.

Hi Andrew,

Both behaviours have pros and cons.  For trees where you build & test
the whole thing, checking in the whole thing makes more sense.

If you want to check in only the changes from the current directory
down then "bzr commit ." will do that.  That should also work for all
other commands.  Maybe this should be explained more in the tutorial.

-- 
Martin