bzr status and commit strange behaviour

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefano Spinucci wrote:
> On 3/17/07, Alexander Belchenko <bialix at ukr.net> wrote:
> As you said replying to my first message to this list
> (https://lists.ubuntu.com/archives/bazaar/2007q1/023251.html):
> "There is absolutely NO problems to store repo on any disk.
> Bazaar supports usual hard drives, USB flash disks, UNC shared
> network locations, and even file network protocols as SFTP/FTP."

> Maybe I misinterpreted your reply and I should not use bazaar with the
> repo stored on a shared network location ???

I think this misunderstanding might be because of terminology
differences.  To us, a repository is just a place to store revisions and
branches.  It is created with the init-repo command.  It is not the
place where you edit and commit your files-- that's called a "working tree".

So Alexander wasn't referring to working trees when he said "There is
absolutely NO problems to store repo on...UNC shared network locations",
but you thought he was, because to you, "repo" includes "working tree".

When you do "bzr init", by default it creates a "standalone tree", which
contains a repository, a branch and a working tree.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF/I2+0F+nu1YWqI0RArO4AJ98zMVl3KCQ+HJkByXfcOGcgFLmlgCgheXF
seQ2gX8L2GcnlHpUEKWBbro=
=2qBz
-----END PGP SIGNATURE-----