{"thread":{"id":"37333","subject":"Problem with Git rev-list output","startedAt":"2014-08-12T01:10:28Z","lastAt":"2014-08-12T01:10:28Z","messageCount":1,"participants":["Crabtree, Andrew"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"247601","messageId":"B82B660D4887C042850326C2BC65FE035D5151C3@G9W0768.americas.hpqcorp.net","threadId":"37333","inReplyTo":null,"subject":"Problem with Git rev-list output","fromName":"Crabtree, Andrew","fromEmail":"andrew.crabtree@hp.com","sentAt":"2014-08-12T01:10:28Z","receivedAt":"2014-08-12T01:10:28Z","isPatch":false,"sender":{"key":"andrew.crabtree@hp.com","avatar":null},"body":"I'm seeing some oddity in one of my repositories where the root commit is being output in 'rev-list' even when I pass in a reference that should exclude it from being output.\n\nI've attempted to reproduce the issue in a test environment but so far have failed at that.\n\nProblem details below as best as I can capture them.  \n\nSeeing the issue with versions of git from 1.7 to 2.1.\n\nThanks,\n-Andrew\n\nThe root commit is here \n\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git cat-file -p 848de9c422c01c1f724d5c3f615bec476911f59f\ntree 5be87811b44f560159d9bb6a10a9fe9bd59147b9\nauthor Migration Script <migration@gaia.rose.hp.com> 1318778853 -0700\ncommitter Gustavo Mora Corrales <gustavo.mora.corrales@hp.com> 1318778853 -0700\n\nInitial synchronization commit\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git --version\ngit version 2.1.0.rc2.3.g67de23d\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git merge-base WALLE-J-14-60-GIT_07-DEC-2011 samrom_t4a\n848de9c422c01c1f724d5c3f615bec476911f59f\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list 848de9c422c01c1f724d5c3f615bec476911f59f\n848de9c422c01c1f724d5c3f615bec476911f59f\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list WALLE-J-14-60-GIT_07-DEC-2011 | wc -l \n2132\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list samrom_t4a | wc -l\n316\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list WALLE-J-14-60-GIT_07-DEC-2011 samrom_t4a | wc -l\n2447\n\n# commit is reachable from both references as expected \n\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list WALLE-J-14-60-GIT_07-DEC-2011 | grep 848de9c422c01c1f724d5c3f615bec476911f59f\n848de9c422c01c1f724d5c3f615bec476911f59f\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list samrom_t4a | grep 848de9c422c01c1f724d5c3f615bec476911f59f\n848de9c422c01c1f724d5c3f615bec476911f59f\n\n# Here -I would have expected --preceding the SHA with -boundary specified\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list --boundary WALLE-J-14-60-GIT_07-DEC-2011 samrom_t4a | grep 848de9c422c01c1f724d5c3f615bec476911f59f\n848de9c422c01c1f724d5c3f615bec476911f59f\n\n# here I don't expect the SHA to show up with either command line.\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list WALLE-J-14-60-GIT_07-DEC-2011 ^samrom_t4a | grep 848de9c422c01c1f724d5c3f615bec476911f59f\n848de9c422c01c1f724d5c3f615bec476911f59f\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$ git rev-list samrom_t4a ^WALLE-J-14-60-GIT_07-DEC-2011 | grep 848de9c422c01c1f724d5c3f615bec476911f59f\nme@myvm:/pnb/software/userrepos/cache/t4_ghs.git  (BARE:titan4_v14_a)$\n"}]}