On Thu, 2013-10-03 at 09:16 +0000, Stanacar, StefanX wrote: >
> Also: > [stefans@firebird poky2]$ git tag -l --contains > 0197e5cb4253d6137b0d166cfcd699d404d2cab3 > 1.5_M5.rc6 > [stefans@firebird poky2]$ git tag -l --contains > a02280f99f05b1c21de2a78de9222a2f62a0dabc > 1.5_M5.rc6 > [stefans@firebird poky2]$ git tag -v 1.5_M5.rc6 > object a02280f99f05b1c21de2a78de9222a2f62a0dabc > type commit > tag 1.5_M5.rc6 > > I don't know how git rev-parse is supposed to work on a tag and why it > returns a different id, but it's a bit confusing. > Okay this tagging thing confuses me, although everything seems to be in orderd the ids are identical. If someone with more git-fu can explain what and how this happens I'd be grateful: [stefans@firebird poky]$ git rev-list 1.5_M5.rc6 | head -n1 a02280f99f05b1c21de2a78de9222a2f62a0dabc [stefans@firebird poky]$ git show-ref 1.5_M5.rc6 0197e5cb4253d6137b0d166cfcd699d404d2cab3 refs/tags/1.5_M5.rc6 [stefans@firebird poky]$ git rev-parse 1.5_M5.rc6 0197e5cb4253d6137b0d166cfcd699d404d2cab3 [stefans@firebird poky]$ git rev-parse --verify 1.5_M5.rc6^{commit} a02280f99f05b1c21de2a78de9222a2f62a0dabc [stefans@firebird poky]$ git show-ref --dereference 1.5_M5.rc6 0197e5cb4253d6137b0d166cfcd699d404d2cab3 refs/tags/1.5_M5.rc6 a02280f99f05b1c21de2a78de9222a2f62a0dabc refs/tags/1.5_M5.rc6^{} [stefans@firebird poky]$ Cheers, Stefan > Cheers, > > Stefan > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto