From: Jacob Keller <jacob.e.keller@intel.com>
To: M Hickford <mirth.hickford@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: How to exclude tagged commits from git log <revision-range>?
Date: Wed, 25 Jun 2025 14:26:50 -0700 [thread overview]
Message-ID: <0595f247-745f-4d57-9d20-4c2065b6c902@intel.com> (raw)
In-Reply-To: <CAGJzqskFuQqLHgFk97S9uaBB=iW2Ni=NWokHJzMV5rYGsCOG4g@mail.gmail.com>
On 6/25/2025 1:30 PM, M Hickford wrote:
> Hi. Is it possible to exclude tagged commits from a revision range?
>
> I tried
>
> git log --exclude=ref/tags/v* v2.3.0..v2.4.0
>
> but this didn't exclude any commits.
>
> An inelegant workaround is:
>
> git log --oneline --decorate v2.3.0..v2.4.0 | grep --invert-match "tag: v"
>
What is your actual end goal with this git log? Why do you want to not
see tag commits?
I think your "inelegant" solution may be the only way to get what you want.
prev parent reply other threads:[~2025-06-25 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 20:30 How to exclude tagged commits from git log <revision-range>? M Hickford
2025-06-25 20:47 ` Junio C Hamano
2025-06-25 21:26 ` Jacob Keller [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=0595f247-745f-4d57-9d20-4c2065b6c902@intel.com \
--to=jacob.e.keller@intel.com \
--cc=git@vger.kernel.org \
--cc=mirth.hickford@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox