Re: [BUG] --bare is ignored before command word

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Nov 18, 2015, 21:29 UTC
Message-ID: <vpqa8qbov2n.fsf@anie.imag.fr>
In-Reply-To: <CA+P7+xoD2-eDZQt29KBqZF2g4i+K7XhJG0mhUgqf5iDURBPntg@mail.gmail.com>

Jacob Keller <jacob.keller@gmail.com> writes:

Show 14 quoted lines

> On Wed, Nov 18, 2015 at 9:20 AM, Ronny Borchert <mister_rs@web.de> wrote:
>> I was trying to clone a bare repository. Not sure why I did, maybe
>> description on website was wrong.
>> My try:
>>
>> git --bare clone https://github.....
>>
>> This was leading in creating a none bare repository! No error or warning
>> message here!
>> I guess this behavior is also for other --xxx commands.
>>
>
> This is how the git options work. Options before a command word are
> always ignored.

No, they are not ignored. For example

$ git --foobar init Unknown option: --foobar

=> the option is processed, and rejected explicitly.

But as you say, options before the command word apply to "git", not to the particular command. The case of --bare is a bit unfortunate: both "git" and "git clone" accept a --bare option, with a different meaning (read "man git" to find what the first does).

So, I wouldn't call the current behavior a really good one, but it's the documented behavior.

It would be nice to warn in this case though: I don't see any use for "git --bare clone".

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/