Jelmer Vernooij wrote: > There are no requirements on what a revid is in bzr. It's a unique > identifier, nothing more. It can be whatever you like, as long as it's > unique for that specific commit. The committer+date+random_number is > just what bzr uses at the moment to create those unique identifiers. In unpacked git repository commit-id is also commit address. Pack files adds another level of indirection via pack index file. And functions as checksum. P.S. I'm interested what are bzr equivalents of git different types of objects: commits (revision info) and what is stored in there besides commit message and "snapshot"; trees/manifest i.e. how files are gathered together to form given revision; blob i.e. what is the storage format and how it is divided: changeset-like of Arch or file "buckets" of Mercurial and CVS, or something yet different together. Is there equivalent of git tags and tags objects? -- Jakub Narebski Poland - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html