git pull from remote but no such ref was fetched?
I have a git mirror on my disk and when I want to update my repo with git pull it gives me error message:
Your configuration specifies to merge with the ref '3.5/master' from the remote, but no such ref was fetched.
It also gives me:
1ce6dac..a5ab7de 3.4/bfq -> origin/3.4/bfq
fa52ab1..f5d387e 3.4/master -> origin/3.4/master
398cc33..1c3000a 3.4/upstream-updates -> origin/3.4/upstream-updates
d01630e..6b612f7 3.7/master -> origin/3.7/master
491e78a..f49f47f 3.7/misc -> origin/3.7/misc
5b7be63..356d8c6 3.7/upstream-updates -> origin/3.7/upstream-updates
636753a..027c1f3 3.8/master -> origin/3.8/master
b8e524c..cfcf7b5 3.8/misc -> origin/3.8/misc
* [neuer Zweig] 3.8/upstream-updates -> origin/3.8/upstream-updates
When I run make menuconfig it gives me Linux version 3.5.7? What does this mean? How can I update my repo?
git
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
add a comment |
I have a git mirror on my disk and when I want to update my repo with git pull it gives me error message:
Your configuration specifies to merge with the ref '3.5/master' from the remote, but no such ref was fetched.
It also gives me:
1ce6dac..a5ab7de 3.4/bfq -> origin/3.4/bfq
fa52ab1..f5d387e 3.4/master -> origin/3.4/master
398cc33..1c3000a 3.4/upstream-updates -> origin/3.4/upstream-updates
d01630e..6b612f7 3.7/master -> origin/3.7/master
491e78a..f49f47f 3.7/misc -> origin/3.7/misc
5b7be63..356d8c6 3.7/upstream-updates -> origin/3.7/upstream-updates
636753a..027c1f3 3.8/master -> origin/3.8/master
b8e524c..cfcf7b5 3.8/misc -> origin/3.8/misc
* [neuer Zweig] 3.8/upstream-updates -> origin/3.8/upstream-updates
When I run make menuconfig it gives me Linux version 3.5.7? What does this mean? How can I update my repo?
git
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
add a comment |
I have a git mirror on my disk and when I want to update my repo with git pull it gives me error message:
Your configuration specifies to merge with the ref '3.5/master' from the remote, but no such ref was fetched.
It also gives me:
1ce6dac..a5ab7de 3.4/bfq -> origin/3.4/bfq
fa52ab1..f5d387e 3.4/master -> origin/3.4/master
398cc33..1c3000a 3.4/upstream-updates -> origin/3.4/upstream-updates
d01630e..6b612f7 3.7/master -> origin/3.7/master
491e78a..f49f47f 3.7/misc -> origin/3.7/misc
5b7be63..356d8c6 3.7/upstream-updates -> origin/3.7/upstream-updates
636753a..027c1f3 3.8/master -> origin/3.8/master
b8e524c..cfcf7b5 3.8/misc -> origin/3.8/misc
* [neuer Zweig] 3.8/upstream-updates -> origin/3.8/upstream-updates
When I run make menuconfig it gives me Linux version 3.5.7? What does this mean? How can I update my repo?
git
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
I have a git mirror on my disk and when I want to update my repo with git pull it gives me error message:
Your configuration specifies to merge with the ref '3.5/master' from the remote, but no such ref was fetched.
It also gives me:
1ce6dac..a5ab7de 3.4/bfq -> origin/3.4/bfq
fa52ab1..f5d387e 3.4/master -> origin/3.4/master
398cc33..1c3000a 3.4/upstream-updates -> origin/3.4/upstream-updates
d01630e..6b612f7 3.7/master -> origin/3.7/master
491e78a..f49f47f 3.7/misc -> origin/3.7/misc
5b7be63..356d8c6 3.7/upstream-updates -> origin/3.7/upstream-updates
636753a..027c1f3 3.8/master -> origin/3.8/master
b8e524c..cfcf7b5 3.8/misc -> origin/3.8/misc
* [neuer Zweig] 3.8/upstream-updates -> origin/3.8/upstream-updates
When I run make menuconfig it gives me Linux version 3.5.7? What does this mean? How can I update my repo?
git
git
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
edited Mar 1 '13 at 23:39
Gilles
543k12811001617
543k12811001617
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
asked Mar 1 '13 at 13:35
BytemainBytemain
2,27142032
2,27142032
add a comment |
add a comment |
9 Answers
9
active
oldest
votes
Check the branch you are on (git branch), check the configuration for that branch (in .../.git/config), you probably are on the wrong branch or your configuration for it tells to merge with a (now?) non-existent remote branch.
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
20
To remove non-existent remote branch references in your local repository, usegit remote prune origin.
– jevon
Apr 9 '14 at 2:53
7
Another way to "check the configuration" for a branch is:git branch -vv. That displays the branch's associated "remote".
– offby1
Oct 14 '14 at 19:11
add a comment |
In my case, my local branch was not set to track the remote branch. I had to manually run:
git pull origin remotebranch
Then next time you do a push do "git push -u" to set up correct tracking.
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
The same goes for when you first clone an empty repo ie created usinggit init --bare
– Cyclonecode
Mar 25 '15 at 23:21
add a comment |
In my case, my local branch and remote branch had different capitalization.
To resolve this I deleted my local branch $ git branch -d branch-name, then checked out the remote branch again using $ git fetch and $ git checkout Branch-name.
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
Its clean, simple and working fine. Thank you.
– Balasubramani M
Jun 15 '15 at 9:47
I got this error in cmd line. Tried SmartGit with a rebase and got past it.
– P.Brian.Mackey
Nov 4 '16 at 17:26
Do this once instead of delete branch and re-checkout branch every single time: Correct capitalization in your /.git/config
– wz366
May 30 '18 at 22:18
add a comment |
It's possible that someone else on your team simply merged your branch and deleted it (commonly done after merging). You can make the branch on the repo and try again. It's happens to me at my company every once in a while (bitbucket defaults to merge and delete).
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
add a comment |
In my case (the usual caveat), I already had a branch of the appropriate name so I only had to add remote = origin to my .git/config:
[branch "sparql"]
merge = refs/heads/sparql
remote = origin # <-- added
answered Feb 9 '15 at 9:36
ericPericP
1113
add a comment |
I had the same error when running out of disk space. After resizing the volume, the error was gone.
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
add a comment |
In my case I had to call the following commands manually:
git fetch origin
git merge origin/master
(c) https://stackoverflow.com/a/13800341/741782
edited May 23 '17 at 12:40
Community♦
1
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
add a comment |
I got this issue due to a casing problem that manifests itself on Windows.
My Git config looked like:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/Bug/some_branch
On the server, both "Bug" and "bug" existed as part of multiple branches. Windows can only hold one of these at a time though, due to the file system mapping. Therefore, I manually updated my config to match the server version, which actually solved the pull issue:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/bug/some_branch
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
add a comment |
If the branch is gone,
$ git status
On branch blah_gone_now
Your branch is based on 'origin/1234/blah_gone_now', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
$ git branch --unset-upstream
Then checkout master or whatever you need
answered 2 hours ago
M. C. M.M. C. M.
1
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f66548%2fgit-pull-from-remote-but-no-such-ref-was-fetched%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
Check the branch you are on (git branch), check the configuration for that branch (in .../.git/config), you probably are on the wrong branch or your configuration for it tells to merge with a (now?) non-existent remote branch.
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
20
To remove non-existent remote branch references in your local repository, usegit remote prune origin.
– jevon
Apr 9 '14 at 2:53
7
Another way to "check the configuration" for a branch is:git branch -vv. That displays the branch's associated "remote".
– offby1
Oct 14 '14 at 19:11
add a comment |
Check the branch you are on (git branch), check the configuration for that branch (in .../.git/config), you probably are on the wrong branch or your configuration for it tells to merge with a (now?) non-existent remote branch.
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
20
To remove non-existent remote branch references in your local repository, usegit remote prune origin.
– jevon
Apr 9 '14 at 2:53
7
Another way to "check the configuration" for a branch is:git branch -vv. That displays the branch's associated "remote".
– offby1
Oct 14 '14 at 19:11
add a comment |
Check the branch you are on (git branch), check the configuration for that branch (in .../.git/config), you probably are on the wrong branch or your configuration for it tells to merge with a (now?) non-existent remote branch.
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
Check the branch you are on (git branch), check the configuration for that branch (in .../.git/config), you probably are on the wrong branch or your configuration for it tells to merge with a (now?) non-existent remote branch.
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
answered Mar 4 '13 at 20:51
vonbrandvonbrand
14.3k22745
14.3k22745
20
To remove non-existent remote branch references in your local repository, usegit remote prune origin.
– jevon
Apr 9 '14 at 2:53
7
Another way to "check the configuration" for a branch is:git branch -vv. That displays the branch's associated "remote".
– offby1
Oct 14 '14 at 19:11
add a comment |
20
To remove non-existent remote branch references in your local repository, usegit remote prune origin.
– jevon
Apr 9 '14 at 2:53
7
Another way to "check the configuration" for a branch is:git branch -vv. That displays the branch's associated "remote".
– offby1
Oct 14 '14 at 19:11
20
20
To remove non-existent remote branch references in your local repository, use
git remote prune origin.– jevon
Apr 9 '14 at 2:53
To remove non-existent remote branch references in your local repository, use
git remote prune origin.– jevon
Apr 9 '14 at 2:53
7
7
Another way to "check the configuration" for a branch is:
git branch -vv. That displays the branch's associated "remote".– offby1
Oct 14 '14 at 19:11
Another way to "check the configuration" for a branch is:
git branch -vv. That displays the branch's associated "remote".– offby1
Oct 14 '14 at 19:11
add a comment |
In my case, my local branch was not set to track the remote branch. I had to manually run:
git pull origin remotebranch
Then next time you do a push do "git push -u" to set up correct tracking.
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
The same goes for when you first clone an empty repo ie created usinggit init --bare
– Cyclonecode
Mar 25 '15 at 23:21
add a comment |
In my case, my local branch was not set to track the remote branch. I had to manually run:
git pull origin remotebranch
Then next time you do a push do "git push -u" to set up correct tracking.
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
The same goes for when you first clone an empty repo ie created usinggit init --bare
– Cyclonecode
Mar 25 '15 at 23:21
add a comment |
In my case, my local branch was not set to track the remote branch. I had to manually run:
git pull origin remotebranch
Then next time you do a push do "git push -u" to set up correct tracking.
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
In my case, my local branch was not set to track the remote branch. I had to manually run:
git pull origin remotebranch
Then next time you do a push do "git push -u" to set up correct tracking.
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
answered Apr 13 '14 at 1:38
Mauvis LedfordMauvis Ledford
39134
39134
The same goes for when you first clone an empty repo ie created usinggit init --bare
– Cyclonecode
Mar 25 '15 at 23:21
add a comment |
The same goes for when you first clone an empty repo ie created usinggit init --bare
– Cyclonecode
Mar 25 '15 at 23:21
The same goes for when you first clone an empty repo ie created using
git init --bare– Cyclonecode
Mar 25 '15 at 23:21
The same goes for when you first clone an empty repo ie created using
git init --bare– Cyclonecode
Mar 25 '15 at 23:21
add a comment |
In my case, my local branch and remote branch had different capitalization.
To resolve this I deleted my local branch $ git branch -d branch-name, then checked out the remote branch again using $ git fetch and $ git checkout Branch-name.
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
Its clean, simple and working fine. Thank you.
– Balasubramani M
Jun 15 '15 at 9:47
I got this error in cmd line. Tried SmartGit with a rebase and got past it.
– P.Brian.Mackey
Nov 4 '16 at 17:26
Do this once instead of delete branch and re-checkout branch every single time: Correct capitalization in your /.git/config
– wz366
May 30 '18 at 22:18
add a comment |
In my case, my local branch and remote branch had different capitalization.
To resolve this I deleted my local branch $ git branch -d branch-name, then checked out the remote branch again using $ git fetch and $ git checkout Branch-name.
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
Its clean, simple and working fine. Thank you.
– Balasubramani M
Jun 15 '15 at 9:47
I got this error in cmd line. Tried SmartGit with a rebase and got past it.
– P.Brian.Mackey
Nov 4 '16 at 17:26
Do this once instead of delete branch and re-checkout branch every single time: Correct capitalization in your /.git/config
– wz366
May 30 '18 at 22:18
add a comment |
In my case, my local branch and remote branch had different capitalization.
To resolve this I deleted my local branch $ git branch -d branch-name, then checked out the remote branch again using $ git fetch and $ git checkout Branch-name.
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
In my case, my local branch and remote branch had different capitalization.
To resolve this I deleted my local branch $ git branch -d branch-name, then checked out the remote branch again using $ git fetch and $ git checkout Branch-name.
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
answered Nov 7 '14 at 19:58
FeckmoreFeckmore
20123
20123
Its clean, simple and working fine. Thank you.
– Balasubramani M
Jun 15 '15 at 9:47
I got this error in cmd line. Tried SmartGit with a rebase and got past it.
– P.Brian.Mackey
Nov 4 '16 at 17:26
Do this once instead of delete branch and re-checkout branch every single time: Correct capitalization in your /.git/config
– wz366
May 30 '18 at 22:18
add a comment |
Its clean, simple and working fine. Thank you.
– Balasubramani M
Jun 15 '15 at 9:47
I got this error in cmd line. Tried SmartGit with a rebase and got past it.
– P.Brian.Mackey
Nov 4 '16 at 17:26
Do this once instead of delete branch and re-checkout branch every single time: Correct capitalization in your /.git/config
– wz366
May 30 '18 at 22:18
Its clean, simple and working fine. Thank you.
– Balasubramani M
Jun 15 '15 at 9:47
Its clean, simple and working fine. Thank you.
– Balasubramani M
Jun 15 '15 at 9:47
I got this error in cmd line. Tried SmartGit with a rebase and got past it.
– P.Brian.Mackey
Nov 4 '16 at 17:26
I got this error in cmd line. Tried SmartGit with a rebase and got past it.
– P.Brian.Mackey
Nov 4 '16 at 17:26
Do this once instead of delete branch and re-checkout branch every single time: Correct capitalization in your /.git/config
– wz366
May 30 '18 at 22:18
Do this once instead of delete branch and re-checkout branch every single time: Correct capitalization in your /.git/config
– wz366
May 30 '18 at 22:18
add a comment |
It's possible that someone else on your team simply merged your branch and deleted it (commonly done after merging). You can make the branch on the repo and try again. It's happens to me at my company every once in a while (bitbucket defaults to merge and delete).
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
add a comment |
It's possible that someone else on your team simply merged your branch and deleted it (commonly done after merging). You can make the branch on the repo and try again. It's happens to me at my company every once in a while (bitbucket defaults to merge and delete).
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
add a comment |
It's possible that someone else on your team simply merged your branch and deleted it (commonly done after merging). You can make the branch on the repo and try again. It's happens to me at my company every once in a while (bitbucket defaults to merge and delete).
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
It's possible that someone else on your team simply merged your branch and deleted it (commonly done after merging). You can make the branch on the repo and try again. It's happens to me at my company every once in a while (bitbucket defaults to merge and delete).
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
answered Sep 21 '15 at 21:08
Scott BiggsScott Biggs
1213
1213
add a comment |
add a comment |
In my case (the usual caveat), I already had a branch of the appropriate name so I only had to add remote = origin to my .git/config:
[branch "sparql"]
merge = refs/heads/sparql
remote = origin # <-- added
answered Feb 9 '15 at 9:36
ericPericP
1113
add a comment |
In my case (the usual caveat), I already had a branch of the appropriate name so I only had to add remote = origin to my .git/config:
[branch "sparql"]
merge = refs/heads/sparql
remote = origin # <-- added
answered Feb 9 '15 at 9:36
ericPericP
1113
add a comment |
In my case (the usual caveat), I already had a branch of the appropriate name so I only had to add remote = origin to my .git/config:
[branch "sparql"]
merge = refs/heads/sparql
remote = origin # <-- added
answered Feb 9 '15 at 9:36
ericPericP
1113
In my case (the usual caveat), I already had a branch of the appropriate name so I only had to add remote = origin to my .git/config:
[branch "sparql"]
merge = refs/heads/sparql
remote = origin # <-- added
answered Feb 9 '15 at 9:36
ericPericP
1113
answered Feb 9 '15 at 9:36
ericPericP
1113
answered Feb 9 '15 at 9:36
ericPericP
1113
answered Feb 9 '15 at 9:36
ericPericP
1113
1113
add a comment |
add a comment |
I had the same error when running out of disk space. After resizing the volume, the error was gone.
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
add a comment |
I had the same error when running out of disk space. After resizing the volume, the error was gone.
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
add a comment |
I had the same error when running out of disk space. After resizing the volume, the error was gone.
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
I had the same error when running out of disk space. After resizing the volume, the error was gone.
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
answered Nov 22 '16 at 10:24
Daniel AlderDaniel Alder
473618
473618
add a comment |
add a comment |
In my case I had to call the following commands manually:
git fetch origin
git merge origin/master
(c) https://stackoverflow.com/a/13800341/741782
edited May 23 '17 at 12:40
Community♦
1
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
add a comment |
In my case I had to call the following commands manually:
git fetch origin
git merge origin/master
(c) https://stackoverflow.com/a/13800341/741782
edited May 23 '17 at 12:40
Community♦
1
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
add a comment |
In my case I had to call the following commands manually:
git fetch origin
git merge origin/master
(c) https://stackoverflow.com/a/13800341/741782
edited May 23 '17 at 12:40
Community♦
1
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
In my case I had to call the following commands manually:
git fetch origin
git merge origin/master
(c) https://stackoverflow.com/a/13800341/741782
edited May 23 '17 at 12:40
Community♦
1
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
edited May 23 '17 at 12:40
Community♦
1
edited May 23 '17 at 12:40
Community♦
1
edited May 23 '17 at 12:40
Community♦
1
1
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
answered Oct 11 '16 at 2:03
antongorodezkiyantongorodezkiy
1011
1011
add a comment |
add a comment |
I got this issue due to a casing problem that manifests itself on Windows.
My Git config looked like:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/Bug/some_branch
On the server, both "Bug" and "bug" existed as part of multiple branches. Windows can only hold one of these at a time though, due to the file system mapping. Therefore, I manually updated my config to match the server version, which actually solved the pull issue:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/bug/some_branch
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
add a comment |
I got this issue due to a casing problem that manifests itself on Windows.
My Git config looked like:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/Bug/some_branch
On the server, both "Bug" and "bug" existed as part of multiple branches. Windows can only hold one of these at a time though, due to the file system mapping. Therefore, I manually updated my config to match the server version, which actually solved the pull issue:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/bug/some_branch
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
add a comment |
I got this issue due to a casing problem that manifests itself on Windows.
My Git config looked like:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/Bug/some_branch
On the server, both "Bug" and "bug" existed as part of multiple branches. Windows can only hold one of these at a time though, due to the file system mapping. Therefore, I manually updated my config to match the server version, which actually solved the pull issue:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/bug/some_branch
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
I got this issue due to a casing problem that manifests itself on Windows.
My Git config looked like:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/Bug/some_branch
On the server, both "Bug" and "bug" existed as part of multiple branches. Windows can only hold one of these at a time though, due to the file system mapping. Therefore, I manually updated my config to match the server version, which actually solved the pull issue:
[branch "Bug/some_branch"]
remote = origin
merge = refs/heads/bug/some_branch
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
answered Jul 9 '18 at 12:34
Grimace of DespairGrimace of Despair
1011
1011
add a comment |
add a comment |
If the branch is gone,
$ git status
On branch blah_gone_now
Your branch is based on 'origin/1234/blah_gone_now', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
$ git branch --unset-upstream
Then checkout master or whatever you need
answered 2 hours ago
M. C. M.M. C. M.
1
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
If the branch is gone,
$ git status
On branch blah_gone_now
Your branch is based on 'origin/1234/blah_gone_now', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
$ git branch --unset-upstream
Then checkout master or whatever you need
answered 2 hours ago
M. C. M.M. C. M.
1
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
If the branch is gone,
$ git status
On branch blah_gone_now
Your branch is based on 'origin/1234/blah_gone_now', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
$ git branch --unset-upstream
Then checkout master or whatever you need
answered 2 hours ago
M. C. M.M. C. M.
1
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
If the branch is gone,
$ git status
On branch blah_gone_now
Your branch is based on 'origin/1234/blah_gone_now', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
$ git branch --unset-upstream
Then checkout master or whatever you need
answered 2 hours ago
M. C. M.M. C. M.
1
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
M. C. M.M. C. M.
1
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
M. C. M.M. C. M.
1
answered 2 hours ago
M. C. M.M. C. M.
1
1
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
M. C. M. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f66548%2fgit-pull-from-remote-but-no-such-ref-was-fetched%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
