From: Danil Semelenov <mail@danil.mobi>
To: git@vger.kernel.org
Subject: Bug in git-sh-prompt: incorrectly determines the upstream for repos produced by recent git svn clone --stdlayout
Date: Thu, 4 Feb 2016 01:48:15 +0300 [thread overview]
Message-ID: <20160203224814.GA11100@desktop> (raw)
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.
>I recently did a git svn clone of the Planet Debian SVN and I noticed
>that the normal upstream indicator in the git part of my $PS1 was not
>working properly. The issue appears to be that the code decides that
>the upstream is trunk instead of origin/trunk. trunk gives an error
>from git rev-list but origin/trunk does not. It works for normal git
>svn clone because there the remote branch is just named git-svn with
>no origin/ prefix. I'm using the below settings for my bash git PS1.
>In case you need a small repo to reproduce this with, try neomis.
>It still works with some of my old repos because the remote branch is
>just trunk instead of origin/trunk, so I think git-svn changed this.
reply other threads:[~2016-02-03 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160203224814.GA11100@desktop \
--to=mail@danil.mobi \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.