Hello,
In the RELEASE INFORMATION section of the hammer v0.94.3 issue tracker [1]
the git commit SHA1 is: b2503b0e15c0b13f480f0835060479717b9cf935
On the github page for Ceph Release v0.94.3 [2], when I click on the "95cefea" link [3]
In the RELEASE INFORMATION section of the hammer v0.94.3 issue tracker [1]
the git commit SHA1 is: b2503b0e15c0b13f480f0835060479717b9cf935
On the github page for Ceph Release v0.94.3 [2], when I click on the "95cefea" link [3]
we see the commit SHA1 of: 95cefea9fd9ab740263bf8bb4796fd864d9afe2b
[1] http://tracker.ceph.com/issues/11990
[2] https://github.com/ceph/ceph/releases/tag/v0.94.3
[3] https://github.com/ceph/ceph/commit/95cefea9fd9ab740263bf8bb4796fd864d9afe2b
I'm looking forward to learning...
[1] http://tracker.ceph.com/issues/11990
[2] https://github.com/ceph/ceph/releases/tag/v0.94.3
[3] https://github.com/ceph/ceph/commit/95cefea9fd9ab740263bf8bb4796fd864d9afe2b
I'm looking forward to learning...
Why the different SHA1 values in two places that reference v0.94.3?
Thanks for reading my question!
Thanks for reading my question!
PS: Tried to send this to ceph-dev but Gmail can't send plain text e-mails, evidently.
So annoying! Maybe somebody knows the trick if it is even possible.
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
