git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: dooagain <dooagain@protonmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Bug: git pull output and case sensitivity.
Date: Sat, 18 Mar 2023 19:23:47 +0000	[thread overview]
Message-ID: <WqmlETIn522shWOyopuARwNyw2_6uC5DpGd8FNNO1n5KWp7io9MGwcMBNEkOWVCMm9mOcT_XGZXkpERIE78eFkbvIbWpWAfGALwMi44f6xg=@protonmail.com> (raw)

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)

I configured my git repository to ignore case by executing `git config core.ignorecase true` then I executed `git pull` multiple times.

What did you expect to happen? (Expected behavior)

I expected the output of `git pull` to accurately tell me about new branches.

What happened instead? (Actual behavior)

The output from `git pull` repeatedly claims that remote branches that differ in casing only to my local ref are always considered "new" even when they exist locally and are in sync with the remote branch.

What's different between what you expected and what actually happened?

Here is one example from the output from `git pull`:

* [new branch]              bug/#30k8z31/fixing_affordable_merge_fields -> origin/bug/#30k8z31/fixing_affordable_merge_fields

This is my local ref file:

.git/refs/remotes/origin/Bug/#30k8z31/fixing_affordable_merge_fields

The contents of my local ref is the same commit hash as the remote branch.

Anything else you want to add:

To me this seems like `git pull` is working as expected, but the output seems incorrect.
This is problematic, because in the current repository there are hundreds of branches that generate this output
so when `git pull` actually does have a problem it is very easy to miss.

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.40.0
cpu: arm64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000 arm64
compiler info: clang: 14.0.0 (clang-1400.0.29.202)
libc info: no libc information available
$SHELL (typically, interactive shell): /opt/homebrew/bin/bash


[Enabled Hooks]

             reply	other threads:[~2023-03-18 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 19:23 dooagain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-18 19:21 Bug: git pull output and case sensitivity dooagain
2023-03-19  6:22 ` Torsten Bögershausen
2023-03-20 17:16   ` Jeff King
2023-03-20 18:01     ` dooagain
2023-03-20 19:12       ` Torsten Bögershausen
2023-03-22 17:44         ` dooagain

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='WqmlETIn522shWOyopuARwNyw2_6uC5DpGd8FNNO1n5KWp7io9MGwcMBNEkOWVCMm9mOcT_XGZXkpERIE78eFkbvIbWpWAfGALwMi44f6xg=@protonmail.com' \
    --to=dooagain@protonmail.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).