On Fri, Oct 30, 2015 at 9:51 PM, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > On Fri, Oct 30, 2015 at 6:20 PM, Artie Ziff <artie.ziff@xxxxxxxxx> wrote: >> Hello, >> >> In the RELEASE INFORMATION section of the hammer v0.94.3 issue tracker [1] >> the git commit SHA1 is: b2503b0e15c0b13f480f0835060479717b9cf935 I don't know why they state this commit in the tracker. >> >> 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... >> Why the different SHA1 values in two places that reference v0.94.3? Usually when we cut a release and the information says "this is the hash that should be used to cut a release" it doesn't mean that will be the final hash when released because during the build process changes are made to debian and rpm files so that the new version is "stamped". These changes are then committed which ends up creating a new hash at the tip of the release tag. > > Odd. It's probably to do with that PGP signing in one of the commits, > but I bet Alfredo knows. The signing process is done after all packages are built and repos are created - this is separate from version control changes. > >> >> 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. > > http://lmgtfy.com/?q=gmail+plain+text :) > >> >> >> >> >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |