{"thread":{"id":"41323","subject":"Bug in git-sh-prompt: incorrectly determines the upstream for repos produced by recent git svn clone --stdlayout","startedAt":"2016-02-03T22:48:15Z","lastAt":"2016-02-03T22:48:15Z","messageCount":1,"participants":["Danil Semelenov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"277343","messageId":"20160203224814.GA11100@desktop","threadId":"41323","inReplyTo":null,"subject":"Bug in git-sh-prompt: incorrectly determines the upstream for repos produced by recent git svn clone --stdlayout","fromName":"Danil Semelenov","fromEmail":"mail@danil.mobi","sentAt":"2016-02-03T22:48:15Z","receivedAt":"2016-02-03T22:48:15Z","isPatch":false,"sender":{"key":"mail@danil.mobi","avatar":null},"body":"Let me copy-paste the original bug report from the Debain mail list by Paul Wise http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1321117. The bug is still reproducible with the latest version of git-prompt.sh.\n\n>I recently did a git svn clone of the Planet Debian SVN and I noticed\n>that the normal upstream indicator in the git part of my $PS1 was not\n>working properly. The issue appears to be that the code decides that\n>the upstream is trunk instead of origin/trunk. trunk gives an error\n>from git rev-list but origin/trunk does not. It works for normal git\n>svn clone because there the remote branch is just named git-svn with\n>no origin/ prefix. I'm using the below settings for my bash git PS1.\n>In case you need a small repo to reproduce this with, try neomis.\n>It still works with some of my old repos because the remote branch is\n>just trunk instead of origin/trunk, so I think git-svn changed this.\n"}]}