2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Ronny Borchert <hidden>
Date: 2016-06-15 23:07:16
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.
From: Jacob Keller <hidden>
Date: 2016-06-15 23:07:16
On Wed, Nov 18, 2015 at 9:20 AM, Ronny Borchert [off-list ref] 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. It may be better to warn about these options though, so that they don't cause errors? The reasoning this is done is because options between git and its command word are used to modify general git behavior, while options after the command word modify each specific command in their own way. Regards, Jake