JFYI, these sha1s *are*, by definition, pointers to these commits. They will be the same in your repository. Try these:
git show 895ca49f (in an updated repository) git log 895ca49f http://git.plt-racket.org/plt/commit/895ca49f http://git.plt-racket.org/plt/log/895ca49f http://git.plt-racket.org/plt/commitdiff/895ca49f http://git.plt-racket.org/plt/tree/895ca49f http://git.plt-racket.org/plt/patch/895ca49f http://git.plt-racket.org/plt/895ca49f http://github.com/plt/racket/commit/895ca49f http://github.com/plt/racket/tree/895ca49f I could have them all listed next to each commit, but just the sha1 is the important bit that all tools will recognize. On Apr 21, Jay McCarthy wrote: > > The "git"ty things [...] commit sha1s aren't useful to me. [...] The > sha1s could be useful if they were links to a Web interface, like > github. On Apr 21, Carl Eastlund wrote: > > [...] > Once I've decided that, then I want to see any other quick reference > information: the hash and so forth. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
