From: Junio C Hamano <gitster@pobox.com>
To: Saurabh Sonar <saurabh.sonar120@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Feature Request - Unique commits list
Date: Thu, 28 Sep 2023 07:07:55 -0700 [thread overview]
Message-ID: <xmqqbkdml7b8.fsf@gitster.g> (raw)
In-Reply-To: <CAJ-L=uAjXB67Zx1BPpdJYF_y1RS+UqwpyTMF1F4o3yO+1o76vg@mail.gmail.com> (Saurabh Sonar's message of "Thu, 28 Sep 2023 13:46:37 +0530")
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").
prev parent reply other threads:[~2023-09-28 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 8:16 Feature Request - Unique commits list Saurabh Sonar
2023-09-28 8:21 ` Kristoffer Haugsbakk
2023-09-28 14:07 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbkdml7b8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=saurabh.sonar120@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.