{"thread":{"id":"13576","subject":"bare --init Vs --init bare","startedAt":"2008-05-19T17:53:13Z","lastAt":"2008-05-29T18:31:27Z","messageCount":12,"participants":["Luciano Rocha","Santi Béjar","Junio C Hamano","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"77279","messageId":"20080519175313.GA17305@bit.office.eurotux.com","threadId":"13576","inReplyTo":null,"subject":"bare --init Vs --init bare","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2008-05-19T17:53:13Z","receivedAt":"2008-05-19T17:53:13Z","isPatch":false,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"\nHello,\n\nThis is odd:\n$ git init --bare\nusage: git-init [-q | --quiet] [--template=] [--shared]\n$ git --bare init\nInitialized empty Git repository in /tmp/1/\n\nMy git version:\n$ git --version\ngit version 1.5.5.1.318.gc99b\n\n(Has two patches on top of origin's\n377d9c409ffe0f0d994b929aeb94716139207b9d, setting default prefix in\nMakefile.)\n\nRegards,\nLuciano Rocha\n\n-- \nLuciano Rocha \nEurotux Informática, S.A. \n"},{"id":"77284","messageId":"8aa486160805191232m76bbc7detdcd2d459c8e572cd@mail.gmail.com","threadId":"13576","inReplyTo":"20080519175313.GA17305@bit.office.eurotux.com","subject":"Re: bare --init Vs --init bare","fromName":"Santi Béjar","fromEmail":"sbejar@gmail.com","sentAt":"2008-05-19T19:32:21Z","receivedAt":"2008-05-19T19:32:21Z","isPatch":false,"sender":{"key":"santi@agolina.net","avatar":null},"body":"On Mon, May 19, 2008 at 7:53 PM, Luciano Rocha wrote:\n>\n> Hello,\n>\n\n> This is odd:\n> $ git init --bare\n> usage: git-init [-q | --quiet] [--template=] [--shared]\n> $ git --bare init\n> Initialized empty Git repository in /tmp/1/\n\nThe first is a flag to the init subcommand (man git-init), and the\nother is a flag to git (man git).\n\nSee also:\n\nhttp://www.google.com/search?q=%22git+init+--bare%22+%22git+--bare+init%22\n\nor equivalent\n\nhttp://kerneltrap.org/mailarchive/git/2007/10/15/344050\n\"should git command and git-command be equivalent?\"\n\nSanti\n\n>\n> My git version:\n> $ git --version\n> git version 1.5.5.1.318.gc99b\n>\n> (Has two patches on top of origin's\n> 377d9c409ffe0f0d994b929aeb94716139207b9d, setting default prefix in\n> Makefile.)\n>\n> Regards,\n> Luciano Rocha\n>\n> --\n> Luciano Rocha \n> Eurotux Informática, S.A. \n>\n"},{"id":"77287","messageId":"20080519201049.GA20981@bit.office.eurotux.com","threadId":"13576","inReplyTo":"8aa486160805191232m76bbc7detdcd2d459c8e572cd@mail.gmail.com","subject":"Re: bare --init Vs --init bare","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2008-05-19T20:10:49Z","receivedAt":"2008-05-19T20:10:49Z","isPatch":false,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"On Mon, May 19, 2008 at 09:32:21PM +0200, Santi Béjar wrote:\n> On Mon, May 19, 2008 at 7:53 PM, Luciano Rocha wrote:\n> >\n> > Hello,\n> >\n> \n> > This is odd:\n> > $ git init --bare\n> > usage: git-init [-q | --quiet] [--template=] [--shared]\n> > $ git --bare init\n> > Initialized empty Git repository in /tmp/1/\n> \n> The first is a flag to the init subcommand (man git-init), and the\n> other is a flag to git (man git).\n> \n> See also:\n> \n> http://www.google.com/search?q=%22git+init+--bare%22+%22git+--bare+init%22\n> \n> or equivalent\n> \n> http://kerneltrap.org/mailarchive/git/2007/10/15/344050\n> \"should git command and git-command be equivalent?\"\n> \n\nOk, I understand.\n\nStill, there's a --bare command to git clone, and I had only tried\ngit init --bare, not the other form, and it always failed. Only today\ndid I learn I could do a git --bare init, from a colleague of mine.\n\nI'd suggest allowing git init --bare, or documenting the --bare init\noption.\n\nRegards,\nLuciano Rocha\n\n-- \nLuciano Rocha \nEurotux Informática, S.A. \n"},{"id":"77334","messageId":"20080520194850.GB19226@bit.office.eurotux.com","threadId":"13576","inReplyTo":"20080519175313.GA17305@bit.office.eurotux.com","subject":"[PATCH] git-init: inform user of `git --bare init' option","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2008-05-20T19:48:50Z","receivedAt":"2008-05-20T19:48:50Z","isPatch":true,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"Creation of a bare repository isn't consistent:\n\n$ git init --bare\nusage: git-init [-q | --quiet] [--template=] [--shared]\n$ git --bare init\nInitialized empty Git repository in ...\n\nDocument the second option, and show an error informing of it if the\nuser calls `git-init' with a `--bare' option.\n\nSigned-off-by: Luciano Rocha \n---\n Documentation/git-init.txt | 2 ++\n builtin-init-db.c | 2 ++\n 2 files changed, 4 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-init.txt b/Documentation/git-init.txt\nindex b17ae84..bb87e58 100644\n--- a/Documentation/git-init.txt\n+++ b/Documentation/git-init.txt\n@@ -84,6 +84,8 @@ Running `git-init` in an existing repository is safe. It will not overwrite\n things that are already there. The primary reason for rerunning `git-init`\n is to pick up newly added templates.\n \n+For creating a bare repository, use the form `git --bare init`.\n+\n Note that `git-init` is the same as `git-init-db`. The command\n was primarily meant to initialize the object database, but over\n time it has become responsible for setting up the other aspects\ndiff --git a/builtin-init-db.c b/builtin-init-db.c\nindex a76f5d3..65454b1 100644\n--- a/builtin-init-db.c\n+++ b/builtin-init-db.c\n@@ -334,6 +334,8 @@ int cmd_init_db(int argc, const char **argv, const char *prefix)\n \t\t\ttemplate_dir = arg+11;\n \t\telse if (!strcmp(arg, \"--shared\"))\n \t\t\tshared_repository = PERM_GROUP;\n+\t\telse if (!strcmp(arg, \"--bare\"))\n+\t\t\tdie(\"Run `git --bare init' instead to create a bare repository\");\n \t\telse if (!prefixcmp(arg, \"--shared=\"))\n \t\t\tshared_repository = git_config_perm(\"arg\", arg+9);\n \t\telse if (!strcmp(arg, \"-q\") || !strcmp(arg, \"--quiet\"))\n-- \n1.5.5.1.317.ge7bcb.dirty\n"},{"id":"77524","messageId":"7vy761sgks.fsf@gitster.siamese.dyndns.org","threadId":"13576","inReplyTo":"20080520194850.GB19226@bit.office.eurotux.com","subject":"Re: [PATCH] git-init: inform user of `git --bare init' option","fromName":"Junio C Hamano","fromEmail":"junio@pobox.com","sentAt":"2008-05-23T06:02:59Z","receivedAt":"2008-05-23T06:02:59Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Luciano Rocha writes:\n\n> Creation of a bare repository isn't consistent:\n>\n> $ git init --bare\n> usage: git-init [-q | --quiet] [--template=] [--shared]\n> $ git --bare init\n> Initialized empty Git repository in ...\n\nThe examples do not demonstrate that \"it isn't consistent\". It just\ndemonstrates that it is easy for people to forget that --bare option is an\noption to the \"git\" potty itself and not an option to \"git init\".\n\n> diff --git a/builtin-init-db.c b/builtin-init-db.c\n> index a76f5d3..65454b1 100644\n> --- a/builtin-init-db.c\n> +++ b/builtin-init-db.c\n> @@ -334,6 +334,8 @@ int cmd_init_db(int argc, const char **argv, const char *prefix)\n> \t\t\ttemplate_dir = arg+11;\n> \t\telse if (!strcmp(arg, \"--shared\"))\n> \t\t\tshared_repository = PERM_GROUP;\n> +\t\telse if (!strcmp(arg, \"--bare\"))\n> +\t\t\tdie(\"Run `git --bare init' instead to create a bare repository\");\n> \t\telse if (!prefixcmp(arg, \"--shared=\"))\n> \t\t\tshared_repository = git_config_perm(\"arg\", arg+9);\n> \t\telse if (!strcmp(arg, \"-q\") || !strcmp(arg, \"--quiet\"))\n\nGiven that you are adding a special case support for \"git init --bare\"\nanyway, a better approach to help people out of this easy confusion (and\nwe have to admit that the confusion is very easy!) would be to make \"git\ninit --bare\" pretend/behave as if the user said \"git --bare init\", don't\nyou think?\n"},{"id":"77555","messageId":"20080523142432.GA8360@bit.office.eurotux.com","threadId":"13576","inReplyTo":"7vy761sgks.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] git-init: inform user of `git --bare init' option","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2008-05-23T14:24:32Z","receivedAt":"2008-05-23T14:24:32Z","isPatch":true,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"On Thu, May 22, 2008 at 11:02:59PM -0700, Junio C Hamano wrote:\n> Luciano Rocha writes:\n> \n> > Creation of a bare repository isn't consistent:\n> >\n> > $ git init --bare\n> > usage: git-init [-q | --quiet] [--template=] [--shared]\n> > $ git --bare init\n> > Initialized empty Git repository in ...\n> \n> The examples do not demonstrate that \"it isn't consistent\". It just\n> demonstrates that it is easy for people to forget that --bare option is an\n> option to the \"git\" potty itself and not an option to \"git init\".\n\nWell, \"git --help init\" works the same as \"git init --help\", so \"--bare\"\nnot working depending on its position isn't very consistent...\n\n\n> Given that you are adding a special case support for \"git init --bare\"\n> anyway, a better approach to help people out of this easy confusion (and\n> we have to admit that the confusion is very easy!) would be to make \"git\n> init --bare\" pretend/behave as if the user said \"git --bare init\", don't\n> you think?\n\nYes, but this was easy for me to do. The proper way, however, will take\nme more time.\n\n-- \nLuciano Rocha \nEurotux Informática, S.A. \n"},{"id":"77969","messageId":"20080528185103.GA4431@bit.office.eurotux.com","threadId":"13576","inReplyTo":"7vy761sgks.fsf@gitster.siamese.dyndns.org","subject":"[PATCH] git-init: treat option `--bare'","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2008-05-28T18:51:03Z","receivedAt":"2008-05-28T18:51:03Z","isPatch":true,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"Currently, passing the `--bare' option to git-init proper doesn't work, and\ngives no indication that `git --bare init' would work instead:\n\n$ git init --bare\nusage: git-init [-q | --quiet] [--template=] [--shared]\n\nTreat the `--bare' option internally in builtin-init-db.\n\nAlso, fix the usage string, synchronising it with the synopsis in the\ndocumentation.\n---\n Documentation/git-init.txt | 7 ++++++-\n builtin-init-db.c | 9 +++++++--\n 2 files changed, 13 insertions(+), 3 deletions(-)\n\nParsing the --bare option correctly (AFAICS) was easier than I expected.\n\ndiff --git a/Documentation/git-init.txt b/Documentation/git-init.txt\nindex b17ae84..b48c312 100644\n--- a/Documentation/git-init.txt\n+++ b/Documentation/git-init.txt\n@@ -8,7 +8,7 @@ git-init - Create an empty git repository or reinitialize an existing one\n \n SYNOPSIS\n --------\n-'git-init' [-q | --quiet] [--template=] [--shared[=]]\n+'git-init' [-q | --quiet] [--bare] [--template=] [--shared[=]]\n \n \n OPTIONS\n@@ -20,6 +20,11 @@ OPTIONS\n \n Only print error and warning messages, all other output will be suppressed.\n \n+--bare::\n+\n+Create a bare repository. If GIT_DIR environment is not set, it is set to the\n+current working directory.\n+\n --template=::\n \n Provide the directory from which templates will be used. The default template\ndiff --git a/builtin-init-db.c b/builtin-init-db.c\nindex d8bdf92..e23b843 100644\n--- a/builtin-init-db.c\n+++ b/builtin-init-db.c\n@@ -364,7 +364,7 @@ static int guess_repository_type(const char *git_dir)\n }\n \n static const char init_db_usage[] =\n-\"git-init [-q | --quiet] [--template=] [--shared]\";\n+\"git-init [-q | --quiet] [--bare] [--template=] [--shared[=]]\";\n \n /*\n * If you want to, you can share the DB area with any number of branches.\n@@ -383,7 +383,12 @@ int cmd_init_db(int argc, const char **argv, const char *prefix)\n \t\tconst char *arg = argv[1];\n \t\tif (!prefixcmp(arg, \"--template=\"))\n \t\t\ttemplate_dir = arg+11;\n-\t\telse if (!strcmp(arg, \"--shared\"))\n+\t\telse if (!strcmp(arg, \"--bare\")) {\n+\t\t\tstatic char git_dir[PATH_MAX+1];\n+\t\t\tis_bare_repository_cfg = 1;\n+\t\t\tsetenv(GIT_DIR_ENVIRONMENT, getcwd(git_dir,\n+\t\t\t\t\t\tsizeof(git_dir)), 0);\n+\t\t} else if (!strcmp(arg, \"--shared\"))\n \t\t\tshared_repository = PERM_GROUP;\n \t\telse if (!prefixcmp(arg, \"--shared=\"))\n \t\t\tshared_repository = git_config_perm(\"arg\", arg+9);\n-- \n1.5.6.rc0.41.gabae7.dirty\n\n"},{"id":"77970","messageId":"20080528185357.GB4431@bit.office.eurotux.com","threadId":"13576","inReplyTo":"20080528185103.GA4431@bit.office.eurotux.com","subject":"Re: [PATCH] git-init: treat option `--bare'","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2008-05-28T18:53:57Z","receivedAt":"2008-05-28T18:53:57Z","isPatch":true,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"Currently, passing the `--bare' option to git-init proper doesn't work, and\ngives no indication that `git --bare init' would work instead:\n\n$ git init --bare\nusage: git-init [-q | --quiet] [--template=] [--shared]\n\nTreat the `--bare' option internally in builtin-init-db.\n\nAlso, fix the usage string, synchronising it with the synopsis in the\ndocumentation.\n\nSigned-off-by: Luciano Rocha \n---\n Documentation/git-init.txt | 7 ++++++-\n builtin-init-db.c | 9 +++++++--\n 2 files changed, 13 insertions(+), 3 deletions(-)\n\nParsing the --bare option correctly (AFAICS) was easier than I expected.\n\nSorry, forgot the Signed-off-by line.\n\ndiff --git a/Documentation/git-init.txt b/Documentation/git-init.txt\nindex b17ae84..b48c312 100644\n--- a/Documentation/git-init.txt\n+++ b/Documentation/git-init.txt\n@@ -8,7 +8,7 @@ git-init - Create an empty git repository or reinitialize an existing one\n \n SYNOPSIS\n --------\n-'git-init' [-q | --quiet] [--template=] [--shared[=]]\n+'git-init' [-q | --quiet] [--bare] [--template=] [--shared[=]]\n \n \n OPTIONS\n@@ -20,6 +20,11 @@ OPTIONS\n \n Only print error and warning messages, all other output will be suppressed.\n \n+--bare::\n+\n+Create a bare repository. If GIT_DIR environment is not set, it is set to the\n+current working directory.\n+\n --template=::\n \n Provide the directory from which templates will be used. The default template\ndiff --git a/builtin-init-db.c b/builtin-init-db.c\nindex d8bdf92..e23b843 100644\n--- a/builtin-init-db.c\n+++ b/builtin-init-db.c\n@@ -364,7 +364,7 @@ static int guess_repository_type(const char *git_dir)\n }\n \n static const char init_db_usage[] =\n-\"git-init [-q | --quiet] [--template=] [--shared]\";\n+\"git-init [-q | --quiet] [--bare] [--template=] [--shared[=]]\";\n \n /*\n * If you want to, you can share the DB area with any number of branches.\n@@ -383,7 +383,12 @@ int cmd_init_db(int argc, const char **argv, const char *prefix)\n \t\tconst char *arg = argv[1];\n \t\tif (!prefixcmp(arg, \"--template=\"))\n \t\t\ttemplate_dir = arg+11;\n-\t\telse if (!strcmp(arg, \"--shared\"))\n+\t\telse if (!strcmp(arg, \"--bare\")) {\n+\t\t\tstatic char git_dir[PATH_MAX+1];\n+\t\t\tis_bare_repository_cfg = 1;\n+\t\t\tsetenv(GIT_DIR_ENVIRONMENT, getcwd(git_dir,\n+\t\t\t\t\t\tsizeof(git_dir)), 0);\n+\t\t} else if (!strcmp(arg, \"--shared\"))\n \t\t\tshared_repository = PERM_GROUP;\n \t\telse if (!prefixcmp(arg, \"--shared=\"))\n \t\t\tshared_repository = git_config_perm(\"arg\", arg+9);\n-- \n1.5.6.rc0.41.gabae7.dirty\n\n"},{"id":"78005","messageId":"7vzlqaq67h.fsf@gitster.siamese.dyndns.org","threadId":"13576","inReplyTo":"20080528185357.GB4431@bit.office.eurotux.com","subject":"Re: [PATCH] git-init: treat option `--bare'","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-05-29T00:55:46Z","receivedAt":"2008-05-29T00:55:46Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Luciano Rocha writes:\n\n> Currently, passing the `--bare' option to git-init proper doesn't work, and\n> gives no indication that `git --bare init' would work instead:\n>\n> $ git init --bare\n> usage: git-init [-q | --quiet] [--template=] [--shared]\n>\n> Treat the `--bare' option internally in builtin-init-db.\n>\n> Also, fix the usage string, synchronising it with the synopsis in the\n> documentation.\n>\n> Signed-off-by: Luciano Rocha \n\nIt could be argued that this kind of \"special casing to help common\nmistake situation\" would in the long run hamper the new users in\nunderstanding what --bare means, because one who uses \"git init --bare\"\nwill not realize that --bare is an option to \"git\" potty in general and\ncan be given when invoking other git commands. On the other hand, many\ncommands do work sensibly inside a bare repository already, and \"init\" is\ntruly special in that it cannot inspect the surroundings to guess if the\nuser wants to create a bare repository or one with a work-tree because\nthere isn't a repository yet. In that sense, probably people not learning\n\"git --bare\" is not such a loss after all.\n\nIn general, I am not particularly fond of this kind of special casing, but\ninitializing a bare repository would be a common enough operation that I\npersonally think it is probably Ok to take this as an exception.\n\nOpinions? Breakages?\n"},{"id":"78027","messageId":"20080529091047.GA21660@bit.office.eurotux.com","threadId":"13576","inReplyTo":"7vzlqaq67h.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] git-init: treat option `--bare'","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2008-05-29T09:10:47Z","receivedAt":"2008-05-29T09:10:47Z","isPatch":true,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"On Wed, May 28, 2008 at 05:55:46PM -0700, Junio C Hamano wrote:\n> Luciano Rocha writes:\n> \n> > Currently, passing the `--bare' option to git-init proper doesn't work, and\n> > gives no indication that `git --bare init' would work instead:\n> >\n> > $ git init --bare\n> > usage: git-init [-q | --quiet] [--template=] [--shared]\n> >\n> > Treat the `--bare' option internally in builtin-init-db.\n> >\n> > Also, fix the usage string, synchronising it with the synopsis in the\n> > documentation.\n> >\n> > Signed-off-by: Luciano Rocha \n> \n> It could be argued that this kind of \"special casing to help common\n> mistake situation\" would in the long run hamper the new users in\n> understanding what --bare means, because one who uses \"git init --bare\"\n> will not realize that --bare is an option to \"git\" potty in general and\n> can be given when invoking other git commands. On the other hand, many\n> commands do work sensibly inside a bare repository already, and \"init\" is\n> truly special in that it cannot inspect the surroundings to guess if the\n> user wants to create a bare repository or one with a work-tree because\n> there isn't a repository yet. In that sense, probably people not learning\n> \"git --bare\" is not such a loss after all.\n> \n> In general, I am not particularly fond of this kind of special casing, but\n> initializing a bare repository would be a common enough operation that I\n> personally think it is probably Ok to take this as an exception.\n> \n> Opinions? Breakages?\n> \n\nPersonally, my first experience with bare repositories, was when I\ndecided to have local mirrors of several projects. As I weren't going to\ndo work over then, I considered copies without a checkout. Reading the\ndocumentation for git-clone, I found the '--bare' option, and found that\nthe commands that I mattered about worked transparently (log, diff,\narchive).\n\nMuch later, when trying to create a public mirror of some of my\nprojects, I tried to create a bare copy. However, as I didn't have\naccess from the remote server to my working copy, I had to push my\nchanges to the remote server.\n\nBut 'git init --bare' didn't work, so I resorted to:\nmirror$ git init\npersonal$ git push mirror:copy\nmirror$ git clone --bare copy public\n\nOnly some time later, in a discussion with a friend, did I learn that\n'git --bare init' worked (and thus this thread was started).\n\nIn my defence, the usage displayed when running just \"git\" hides the\n'--bare' option, as my terminals usually have 24 lines.\n\nAnd the transparently way that the other commands I cared about worked\ninside a bare repository eliminated any need of mine to search for a way\nto specify that I was working with a bare repository to all git commands.\n\nAll in all, you are right when you say that 'this kind of \"special\ncasing\" ... would in the long run hamper the new users ... [by not\nrealizing ] that --bare is an option to \"git\" potty in general', as is\nattested by my ignorance of it. But as there is a valid reason for the\n'--bare' option to git-clone, there is one for git-init.\n\nBut the '--bare' option for \"git\" must be at least mentioned in\nthe documentation for those two commands.\n\n-- \nLuciano Rocha \nEurotux Informática, S.A. \n"},{"id":"78043","messageId":"alpine.DEB.1.00.0805291448161.13507@racer.site.net","threadId":"13576","inReplyTo":"7vzlqaq67h.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] git-init: treat option `--bare'","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-05-29T13:51:06Z","receivedAt":"2008-05-29T13:51:06Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 28 May 2008, Junio C Hamano wrote:\n\n> In general, I am not particularly fond of this kind of special casing, \n> but initializing a bare repository would be a common enough operation \n> that I personally think it is probably Ok to take this as an exception.\n\nI like the Perl way (having multiple options to do the same thing), and do \nnot like the Python way (\"there is only one way to do one thing\").\n\n> Opinions? Breakages?\n\nI like the intent of the patch. It will definitely make initializing \nbare Git repositories easier for new users.\n\nAlso keep in mind that \"git --bare writes:\n\n> Also keep in mind that \"git --bare _really_ rare, at least in my experience. I had to use it exactly _twice_ \n> since I started using Git.\n\nExactly. That is really the contributing factor that I am in favor of\nthis (perhaps redundant from theoretical point of view) addition.\n"}]}