Linus Torvalds wrote: > > On Wed, 18 Oct 2006, Robert Collins wrote: >> >> More commonly though, like git users have 'origin' and 'master' >> branches, bzr users tend to have a branch that is the 'origin' (for bzr >> itself this is usually called bzr.dev), as well as N other branches for >> their own work, which is probably why we haven't seen the need to have a >> ui command to spit out the revnos for an arbitrary branch. > > You mis-understand. > > git doesn't have a "ui command to spit out the revnos for an arbitrary > branch" either. > > Normally, you'd just use the branch-name. Nobody ever uses the SHA1's > directly. With the exception of having sometimes commit-ids in the commit messages, for example "Fixes bug introduced by aabbcc00" (although usually you just write "Fixes bug in some_function in some_file"), and automatically generated This reverts d119e3de13ea1493107bd57381d0ce9c9dd90976 commit. (in addition to 'Revert "<Commit title>") for git-revert generated commit messages. And it is true that you usually use branchname, or branchname~n syntax. Git even has git-name-rev to convert from sha1 to temporary, local ref^m~n... syntax. By the way, git has very powerfull syntax to get revisions, and revision lists. For example "git-rev-list foo bar ^baz" means "list all the commits which are included in foo and bar lineage, but not in baz", or more useful "git log origin..next". How's that in bzr? -- 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