git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: getting a list of changes I commited

From
Luck, Tony <tony.luck@intel.com>
Date
Sep 15, 2005, 19:21 UTC
Message-ID
<B8E391BBE9FE384DAA4C5C003888BE6F04662735@scsmsx401.amr.corp.intel.com>
>Why not just _also_ limit it by what is already merged in my tree?

I can add the "^linus", but I think that with my workflow it will never make a difference. Any commits that got into your tree with a committer line by me will already be in my "oldhead" (how else did you get them?). So "^oldhead ^linus" should always be identical to "^oldhead".

>This is what "--header" (and it's zero termination) is 
>designed for:

Great ... I suspected that everything I needed was already there (after all, all GIT problems are solvable with the right arguments to git-rev-list!)

Show 6 quoted lines
>	git-rev-list --header --no-merges newhead ^oldhead |
>		grep -z "committer .*tony\.luck"
>
>and it will give a nice NUL-terminated output list of just 
>your commits. 
>No complex script necessary.

But "git-shortlog" doesn't like the output from this, so I need a script (or another tip on arguments to git commands).

>Also, the "grep the committer" approach fundamentally doesn't
>work if you ever plan on having sub-lieutenants that work with you and
>that you use git to merge with.
Oh happy day when I have sub-lieutenants :-)
-Tony
Next: Linus Torvalds
Message 1 of 2 in “RE: getting a list of changes I commited”
  1. Luck, TonySep 15, 2005
  2. Linus TorvaldsSep 15, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.