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

Re: Feature Request - Unique commits list

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 28, 2023, 14:07 UTC
Message-ID
<xmqqbkdml7b8.fsf@gitster.g>
In-Reply-To
<CAJ-L=uAjXB67Zx1BPpdJYF_y1RS+UqwpyTMF1F4o3yO+1o76vg@mail.gmail.com>
Saurabh Sonar <saurabh.sonar120@gmail.com> writes:
> After merging the master branch into my local it is hard to find my
> own commits in git history.

I suspect the above may be the other way around (i.e., after the upstream takes some but not all of my changes into their 'master' branch, I want to find out what remaining topics from me are still not accepted by them), but anyway, doesn't something along the lines of

	$ git log --branches --not origin/master
work for you?  It asks
 * Please list commits ("git log")
 * The commits to be listed should be discovered by traversing the
   history starting from my branch tips ("--branches")
 * But I am not interested in those commits that can be reached from
   the 'master' branch of my upstream ("--not origin/master").
Previous: Kristoffer Haugsbakk
Message 3 of 3 in “Feature Request - Unique commits list”
  1. Saurabh SonarSep 28, 2023
  2. Kristoffer HaugsbakkSep 28, 2023
  3. Junio C HamanoSep 28, 2023

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.