-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linus Torvalds wrote:
Right. That's why I said all revisions can be named by a URL + a
number, because it's the combination of the URL + a number that is
unique. (In bzr, each branch has a URL.)
I agree that a revision is a revision, but I don't think that's a
property unique to git. :-)
When two people have copies of the same revision, it's usually because
they are each pulling from a common branch, and so the revision in that
branch can be named. Bazaar does use unique ids internally, but it's
extremely rare that the user needs to use them.
But tags have local meaning only, unless someone has access to your
repository, right?
The key thing about a checkout is that it's stored in a different
location from its repository. This provides a few benefits:
- - you can publish a repository without publishing its working tree,
possibly using standard mirroring tools like rsync.
- - you can have working trees on local systems while having the
repository on a remote system. This makes it easy to work on one
logical branch from multiple locations, without getting out of sync.
- - you can use a checkout to maintain a local mirror of a read-only
branch (I do this with http://bazaar-vcs.com/bzr/bzr.dev).
You can operate that way in bzr too, but I find it nicer to have one
checkout for each active branch, plus a checkout of bzr.dev. Our switch
command also rewrites only the changed part of the working tree.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFNFrv0F+nu1YWqI0RAgBHAJ9XpmdvuCNDysxFhnyeCmkEG/z0ggCggMsJ
WyW6lqGMokh0k0It1KOdgtk=
=L1SR
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html