Jeff King writes:
> On Wed, Nov 18, 2015 at 10:29:20PM +0100, Matthieu Moy wrote:
>
>> 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
On Wed, Nov 18, 2015 at 10:29:20PM +0100, Matthieu Moy wrote:
> 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"
Jacob Keller writes:
> On Wed, Nov 18, 2015 at 9:20 AM, Ronny Borchert 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
On Wed, Nov 18, 2015 at 9:20 AM, Ronny Borchert 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
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.
--
To u
5 matches
Mail list logo