From: Oliver Hoffmann <oliverhoffmann32@googlemail.com>
To: git@vger.kernel.org
Subject: git init --bare versus git --bare init
Date: Sat, 8 May 2010 12:38:13 +0200 [thread overview]
Message-ID: <201005081238.14156.oliverhoffmann32@googlemail.com> (raw)
Hi Git Folk,
If one accidentally writes "git --bare init <dir>" instead of "git init --bare
<dir>" an appended directory argument is ignored and $CUR_DIR or the working
directory will be used:
> pwd
/tmp/foo
> git --bare init /tmp/bar
Initialized empty Git repository in /tmp/foo/
> git init --bare /tmp/bar
Initialized empty Git repository in /tmp/bar/
... but both should probably be initialized in /tmp/bar/
Greetings,
Oliver Hoffmann
next reply other threads:[~2010-05-08 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 10:38 Oliver Hoffmann [this message]
2010-05-10 9:42 ` [PATCH] handle "git --bare init <dir>" properly Jeff King
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=201005081238.14156.oliverhoffmann32@googlemail.com \
--to=oliverhoffmann32@googlemail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).