Repository referencing in command lines

[Aaron Bentley]

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

Matthew D. Fuller wrote:
| But on the other hand, I've figured out one reason why I drew back
| from it, without having a "modules" layer over the branch layer.  The
| "problem" is that the repo has only a single namespace for branches.

I don't really agree with this.  I think what's bothering you is that
bzr doesn't use names to specify location.  We just use locations directly.

| If I'm working on two projects, libfoo and libbar, and each has a
| branch called "main", it won't work; I'd have to call the branches
| libfoo/main and libbar/main.

See, what I'm saying is that $REPO/libfoo/main isn't a name, it's a
location.  The default branch nick for such a branch would indeed be 'main'.

| Now, I say "problem" because it blows up that use-case.  It doesn't so
| much matter if we just put each separate projects in its own
| repository.

I think we do want to support repo branches with minimal fuss.  To me,
this suggests people don't need separate repositories for separate projects.

| If
| that's the way bzr goes (which I understand it to be), I'll just have
| to go that route; it's unsettling, because I like the idea of a repo
| being "All my projects go in this one single place", but in the grand
| scheme of things, it's hardly a big deal.

Ah, but is "repo/libfoo/main" really all that different from
"libfoo/main" (where libfoo is the repo for libfoo)?"

| I consider a branch name to be a name, not a path.

We already have branch names, and they're not what you're referring to here.

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

iD8DBQFD7jQc0F+nu1YWqI0RAubqAJ9FU6AiIulk0gnPjDwZyMAhVOJYZgCfcgDY
v9EqwPI/ug+e4TGD/sm26oc=
=LrAu
-----END PGP SIGNATURE-----