{"thread":{"id":"35404","subject":"Filter log based on paths NOT touched","startedAt":"2013-11-25T20:20:09Z","lastAt":"2013-11-26T04:34:36Z","messageCount":4,"participants":["Phillip Susi","Junio C Hamano","Duy Nguyen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"231093","messageId":"5293B0F9.1050200@ubuntu.com","threadId":"35404","inReplyTo":null,"subject":"Filter log based on paths NOT touched","fromName":"Phillip Susi","fromEmail":"psusi@ubuntu.com","sentAt":"2013-11-25T20:20:09Z","receivedAt":"2013-11-25T20:20:09Z","isPatch":false,"sender":{"key":"psusi@ubuntu.com","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nI can't seem to find a way to invert the meaning of a pathspec given\nto git log in order to find commits touching anything BUT a given\npath. Does such a thing exist?\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v2.0.17 (MingW32)\nComment: Using GnuPG with Thunderbird - http://www.enigmail.net/\n\niQEcBAEBAgAGBQJSk7D5AAoJEJrBOlT6nu75myIIAMoAgihPAhDrCBpRKUHF/X8S\nB8vjwIg7zALajU+vrz7B/UyxKFHC54sYn0MaAA5htBXKCtd6L0tHrNa1gYbd9qT+\nxgTuF7+Unwv90yFBEsoZgEwlSyaLBAVHknMiE4ecxaJrlhBqESbePNrORCwCAuPq\nANrYunEETN2KNgYBkNszdEp7Ga9RcP7LWisL/pNV2k+ac7YfqGp1jsN00jLMYqvH\nc+8Kl154N3xgvk+pGvkKGbO3MavkmEK47lLL929g9iXeP3NkMsrxyEjhnABD9tS3\nSxzYZt9G+lpH2Tv8l1/NqMafdNy5P7CEs00C4JZn1EzEcIBqMeYgUhce+WU75qc=\n=p2gM\n-----END PGP SIGNATURE-----\n"},{"id":"231097","messageId":"xmqqeh64xlqw.fsf@gitster.dls.corp.google.com","threadId":"35404","inReplyTo":"5293B0F9.1050200@ubuntu.com","subject":"Re: Filter log based on paths NOT touched","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-11-25T20:35:51Z","receivedAt":"2013-11-25T20:35:51Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Phillip Susi writes:\n\n> I can't seem to find a way to invert the meaning of a pathspec given\n> to git log in order to find commits touching anything BUT a given\n> path. Does such a thing exist?\n\nNot yet (look for \"negative pathspec\").\n"},{"id":"231122","messageId":"CACsJy8DR-ckmZ8Ey9Gh1fhv17_+mRPmeLdj_7LoCnvc9fnnpTg@mail.gmail.com","threadId":"35404","inReplyTo":"xmqqeh64xlqw.fsf@gitster.dls.corp.google.com","subject":"Re: Filter log based on paths NOT touched","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2013-11-26T03:13:53Z","receivedAt":"2013-11-26T03:13:53Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Tue, Nov 26, 2013 at 3:35 AM, Junio C Hamano wrote:\n> Phillip Susi writes:\n>\n>> I can't seem to find a way to invert the meaning of a pathspec given\n>> to git log in order to find commits touching anything BUT a given\n>> path. Does such a thing exist?\n>\n> Not yet (look for \"negative pathspec\").\n\nThere's a difference between \"skip commits that touch anything\ndirectory foo even if it also touches something outside of foo\" and\n\"skip commits that _only_ touches something in foo\". Not sure which\nway Phillip wants here. Negative pathspec only supports the latter.\nThe former needs a new option in rev-list, because the logic to\nconsider a commit not a match if it matches a pathspec is out of\ntree_entry_interesting()'s control.\n-- \nDuy\n"},{"id":"231123","messageId":"529424DC.6030107@ubuntu.com","threadId":"35404","inReplyTo":"CACsJy8DR-ckmZ8Ey9Gh1fhv17_+mRPmeLdj_7LoCnvc9fnnpTg@mail.gmail.com","subject":"Re: Filter log based on paths NOT touched","fromName":"Phillip Susi","fromEmail":"psusi@ubuntu.com","sentAt":"2013-11-26T04:34:36Z","receivedAt":"2013-11-26T04:34:36Z","isPatch":false,"sender":{"key":"psusi@ubuntu.com","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nOn 11/25/2013 10:13 PM, Duy Nguyen wrote:\n> There's a difference between \"skip commits that touch anything\n> directory foo even if it also touches something outside of foo\" and\n> \"skip commits that _only_ touches something in foo\". Not sure which\n> way Phillip wants here. Negative pathspec only supports the latter.\n> The former needs a new option in rev-list, because the logic to\n> consider a commit not a match if it matches a pathspec is out of\n> tree_entry_interesting()'s control.\n\nI'm looking for the latter. Specifically I'm trying to see what changes to the upstream code a debian package has made so I need to ignore commits that only change things in debian/.\n\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.14 (GNU/Linux)\nComment: Using GnuPG with Thunderbird - http://www.enigmail.net/\n\niQEcBAEBCgAGBQJSlCTcAAoJEJrBOlT6nu75jUQIAJOybMyXE6lr4y4aX6od02Rn\nlINvPVC1Xub2E1lsofIB+N4QvZDRWlIJOIcj3GRqirzUcNBaIOUxUW4+UV7KgMQH\nwmImS8DdBgrkI8Sompe9B0gqd4lmB2mzTutQfOzdEZ/ZOU50935daYboK//X7zM/\nvSmumJpRwNfw1BKyuxVpAQ8Ablo9yUu2cswLKJPSKyQkT9d/AJn07LE5/DKZORQN\nRD3r94kToftgTfsQTJbNpPujJ5nVHwVmiC44Qghdquj54l++ai5Xs2wRU3Za3i+O\nts7Tn5Lrw+pFAT5Lnt0v8Yedp7fVgjRhIsNEDIVlgNuHevP/oBOXIxuLJBlCBIE=\n=AYYO\n-----END PGP SIGNATURE-----\n"}]}