RE: getting a list of changes I commited

From: Luck, Tony <tony.luck@intel.com>
Date: 2005-09-16 06:23:33
>No. "oldhead" has to be the point where you did the last email thing.
>
>So any time you merge from me, next time your email cron-job (or whatever)  
>hits, ^linus _will_ make a difference. Without it, you'd email out all the 
>stuff that came through my tree.

I'm planning on doing this as part of my "push" script.  So
the oldhead is what is already up on kernel.org (which is when
I will have done the previous e-mail).  My "newhead" will be
full of stuff I got from your tree ... but most of the things
I pull from you were commited by someone else, so the "grep -z"
will drop them on the floor.  So there are just a few that have
my commit line on them ... but these *must* have come from my tree
(unless someone else is putting my name on commits!). That leaves
me with just my new commits for the e-mail.

>	git-rev-list --header newhead ^oldhead |
>		grep -z "committer .*tony\.luck" |
>		tr '\0' '\n' |
>		git-shortlog

I figured out the "tr" part myself.  That's when I saw that git-shortlog
expected to find "^Author:" and was getting "^author".

-Tony
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Fri Sep 16 06:24:53 2005

This archive was generated by hypermail 2.1.8 : 2005-09-16 06:24:56 EST