git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Sales <vinux.development@gmail.com>
To: git@vger.kernel.org
Subject: I want to report a bug/anomaly in Git
Date: Tue, 11 Jan 2011 22:22:29 +0000	[thread overview]
Message-ID: <AANLkTimt+U3oo4FaywUr86ArG8d29yWAeVYhpRkBYa_K@mail.gmail.com> (raw)

Hi, how do I report a bug/anomaly in git? I have looked on the git
website and tried to ask on the git irc on freenode but couldn't post,
even after requesting a 'voice'. The bug is that if you happen to
create a new remote branch which shares it's name with an existing
directory in the top level of the git repository, git then seems to
get confused and the: git checkout <branch> - command doesn't switch
to that branch or turn tracking on (and seems to think it was created
from origin/<branch> rather than from refs/remotes/origin/<branch>),
which it does if the branch doesn't share a name with an existing top
level directory. This can be rectified by running: git checkout
--track -b debian origin/debian - but this confused me for several
hours and it was only because I had another repository with the same
branch names, but different top level directories where the command
worked that it finally dawned on me what the problem was. I then
deleted the branch and created a new one with a differnt name and
everything worked as expected.

-- 
drbongo

Dig that crazy beat on the drums: <http://vinux.org.uk>  The best is
getting better!

             reply	other threads:[~2011-01-11 22:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 22:22 Tony Sales [this message]
2011-01-12 18:35 ` I want to report a bug/anomaly in Git Jeff King

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=AANLkTimt+U3oo4FaywUr86ArG8d29yWAeVYhpRkBYa_K@mail.gmail.com \
    --to=vinux.development@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.
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 NNTP newsgroup(s).