git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: git@vger.kernel.org
Subject: Ambiguity warning printed twice ?
Date: Thu, 22 Jun 2017 18:16:21 +0530	[thread overview]
Message-ID: <1498135581.2089.1.camel@gmail.com> (raw)

Happy day everyone,

I accidentally noticed a weird behaviour of 'git status'. In a
repository I created a branch with the name 'HEAD' by chance. When I
run 'git status' in the repository it prints a warning about an
ambiguous reference about 'HEAD' which is expected but it prints it
twice which seems suspicious.

    $ git branch
      HEAD
      master
    * test

    $ git status
    warning: refname 'HEAD' is ambiguous.
    warning: refname 'HEAD' is ambiguous.
    On branch test
    ....

Any reasons behind this behaviour or is this a bug?


-- 
Regards,
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>

             reply	other threads:[~2017-06-22 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 12:46 Kaartic Sivaraam [this message]
2017-06-22 14:23 ` Ambiguity warning printed twice ? Jeff King
2017-06-23  2:11   ` Kaartic Sivaraam

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=1498135581.2089.1.camel@gmail.com \
    --to=kaarticsivaraam91196@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).