From: "Torsten Bögershausen" <tboegi@web•de>
To: "André de Castro" <aramosdecastro@gmail•com>, git@vger•kernel.org
Subject: Re: Bug report - Apple git
Date: Mon, 13 Jan 2025 17:35:41 +0100 [thread overview]
Message-ID: <136f18cc-7b6a-4427-a4a7-96ef073ada49@web.de> (raw)
In-Reply-To: <C2871318-4745-4481-9199-72D4544ECD5C@gmail.com>
(Please no top-posting here)
On 2025-01-13 15:23, André de Castro wrote:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
> Checked out a branch, ran "git diff --merge-base <some-annotated-tag> HEAD".
>
> What did you expect to happen? (Expected behavior)
> To see a normal git diff output.
>
> What happened instead? (Actual behavior)
> Didn't get a diff output. Got the following error instead:
> "fatal: --merge-base only works with commits"
>
> What's different between what you expected and what actually happened?
> I didn't get the expected diff output and got an error message instead.
>
> Anything else you want to add:
> Seems it happens when I use a tag as one of the commits for git diff
> --merge-base. This is on a macOS, with apple git.
> On Windows, with Git Bash, it works as expected.
>
> I can get this to work with "git diff --merge-base $(git rev-list -n 1
> <some-annotated-tag>) HEAD".
>
> Please review the rest of the bug report below.
> You can delete any lines you don't wish to share.
>
>
> [System Info]
> git version:
> git version 2.39.5 (Apple Git-154)
> cpu: arm64
> no commit associated with this build
> sizeof-long: 8
> sizeof-size_t: 8
> shell-path: /bin/sh
> feature: fsmonitor--daemon
> uname: Darwin 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec 6 18:56:34 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6020 arm64
> compiler info: clang: 16.0.0 (clang-1600.0.26.6)
> libc info: no libc information available
> $SHELL (typically, interactive shell): /bin/zsh
>
>
> [Enabled Hooks]
> pre-push
>
Hm, I don't think that this group/mailing list takes responsibility
for binaries shipped by companies.
If you want, you can compile Git yourself to be "on par" with
what you find under other OS.
That is the good thing with open source - please let us know,
if help is needed.
next prev parent reply other threads:[~2025-01-13 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 14:23 Bug report - Apple git André de Castro
2025-01-13 16:32 ` Kristoffer Haugsbakk
[not found] ` <B50229FA-0C33-4DFD-B8D9-79F30D616F86@gmail.com>
2025-01-13 16:50 ` André de Castro
2025-01-13 16:35 ` Torsten Bögershausen [this message]
2025-01-14 21:57 ` D. Ben Knoble
2025-01-14 22:43 ` Junio C Hamano
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=136f18cc-7b6a-4427-a4a7-96ef073ada49@web.de \
--to=tboegi@web$(echo .)de \
--cc=aramosdecastro@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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