Git development
 help / color / mirror / Atom feed
From: "Jurko Gospodnetić" <jurko.gospodnetic@docte.hr>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: What is 'git BRANCH'?
Date: Wed, 30 Jul 2008 00:43:35 +0200	[thread overview]
Message-ID: <488F9D17.8020703@docte.hr> (raw)
In-Reply-To: <DEBF93FC-BA8D-4513-B4EE-A8648DA1D591@sb.org>

   Hi all.

> On Jul 29, 2008, at 3:24 PM, Junio C Hamano wrote:
> 
>> Jurko Gospodnetić <jurko.gospodnetic@docte.hr> writes:
>>
>>>  Hi.
>>>
>>>  I typed in "git BRANCH" by accident and got the error message:
>>> "fatal: cannot handle BRANCH internally".
>>>
>>>  What does that mean?
>>>
>>>  It is different from the usual "git: 'yada-yada' is not a
>>> git-command. See 'git --help'." message you get when you type in an
>>> incorrect command name.
>>
>> Just a guess; your git is installed on a case-challenged filesystem?

   Thank you all for explaining this, and yes - this was detected on 
Windows with a NTFS drive set to case-insensitive.

   But, if something is running git-branch here... why does this 
script/executable/whatever try to check the name it got called with? Why 
does it not simply do its work no matter the name it got called with?

   If I'm asking something to obvious here - feel free to send me back 
to read the code... :-)

   Best regards,
     Jurko Gospodnetić

  reply	other threads:[~2008-07-29 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 22:18 What is 'git BRANCH'? Jurko Gospodnetić
2008-07-29 22:24 ` Junio C Hamano
2008-07-29 22:32   ` Kevin Ballard
2008-07-29 22:43     ` Jurko Gospodnetić [this message]
2008-07-29 22:39   ` Junio C Hamano
2008-07-29 22:49     ` Sverre Rabbelier
2008-07-30  5:14       ` Jeff King
2008-07-29 23:45     ` Eric Raible

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=488F9D17.8020703@docte.hr \
    --to=jurko.gospodnetic@docte.hr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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