From: Lee Winder <lee.winder@gmail.com>
To: git@vger.kernel.org
Subject: git fetch --prune removes branches from origin/ with inconsistent case in path names
Date: Tue, 2 Jul 2013 21:37:25 +0100 [thread overview]
Message-ID: <CAJz8ETuFC=STDRbPOxsTDdYbuMh0phdR3AYCzW3AvOrSAmKpWw@mail.gmail.com> (raw)
When using git fetch --prune, git will remove any branches from
remotes/origin/ that have inconsistent case in folder names.
This issue has been verified in versions 1.7.10.2, 1.7.11.1 and 1.8.3.2.
I've described the reproduction steps here as I carried them out, and
listed the plaforms I used to replicate it. The issue will most
likely occur on a different combination of platforms also.
- On Mac, create a new repository and push a master branch to a central server
- On Mac, create a branch called feature/lower_case_branch and push
this to the central server (note that 'feature' is all lower case)
- On Windows, clone the repository but stay on master, do not checkout
the feature/lower_case_branch branch
- On Windows, branch from master a branch called
Feature/upper_case_branch (note the uppercase F) and push to the
server
- On Mac, run git fetch and see that
remote/origin/Feature/upper_case_branch is updated
Couple of things to note here
1) In the git fetch output it lists the branch with an upper case 'F'
* [new branch] Feature/upper_case_branch ->
origin/Feature/upper_case_branch
2) When I run git branch --all it is actually listed with a lower case 'f'
remotes/origin/feature/upper_case_branch
Now the problem happens when I run git fetch --prune, I get the following output
* [new branch] Feature/upper_case_branch ->
origin/Feature/upper_case_branch
x [deleted] (none) -> origin/feature/upper_case_branch
Note the new branch uses 'F' and the deleted branch uses 'f'.
The results of this bug seem to be
* Everytime I call git fetch it thinks Feature/upper_case_branch is a
new branch (if I call 'git branch' multiple times I always get the
[new branch] output)
* Whenever I run with --prune, git will *always* remove the branch
with a different folder name (from a case sensitive perspective) than
the one originally created on the current machine.
Thanks
Lee
next reply other threads:[~2013-07-02 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 20:37 Lee Winder [this message]
2015-03-30 13:58 ` git fetch --prune removes branches from origin/ with inconsistent case in path names Raf 8-)
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='CAJz8ETuFC=STDRbPOxsTDdYbuMh0phdR3AYCzW3AvOrSAmKpWw@mail.gmail.com' \
--to=lee.winder@gmail.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).