{"thread":{"id":"1812","subject":"RE: getting a list of changes I commited","startedAt":"2005-09-15T20:23:33Z","lastAt":"2005-09-15T20:23:33Z","messageCount":1,"participants":["Luck, Tony"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"8634","messageId":"B8E391BBE9FE384DAA4C5C003888BE6F04662802@scsmsx401.amr.corp.intel.com","threadId":"1812","inReplyTo":null,"subject":"RE: getting a list of changes I commited","fromName":"Luck, Tony","fromEmail":"tony.luck@intel.com","sentAt":"2005-09-15T20:23:33Z","receivedAt":"2005-09-15T20:23:33Z","isPatch":false,"sender":{"key":"tony.luck@intel.com","avatar":"https://avatars.githubusercontent.com/u/5446021?v=4"},"body":">No. \"oldhead\" has to be the point where you did the last email thing.\n>\n>So any time you merge from me, next time your email cron-job (or whatever)  \n>hits, ^linus _will_ make a difference. Without it, you'd email out all the \n>stuff that came through my tree.\n\nI'm planning on doing this as part of my \"push\" script.  So\nthe oldhead is what is already up on kernel.org (which is when\nI will have done the previous e-mail).  My \"newhead\" will be\nfull of stuff I got from your tree ... but most of the things\nI pull from you were commited by someone else, so the \"grep -z\"\nwill drop them on the floor.  So there are just a few that have\nmy commit line on them ... but these *must* have come from my tree\n(unless someone else is putting my name on commits!). That leaves\nme with just my new commits for the e-mail.\n\n>\tgit-rev-list --header newhead ^oldhead |\n>\t\tgrep -z \"committer .*tony\\.luck\" |\n>\t\ttr '\\0' '\\n' |\n>\t\tgit-shortlog\n\nI figured out the \"tr\" part myself.  That's when I saw that git-shortlog\nexpected to find \"^Author:\" and was getting \"^author\".\n\n-Tony\n"}]}