From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix initialization of a bare repository
Date: Fri, 17 Aug 2007 23:20:21 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708172319480.20400@racer.site> (raw)
In-Reply-To: <7vhcn0pm3h.fsf@gitster.siamese.dyndns.org>
Hi,
On Wed, 15 Aug 2007, Junio C Hamano wrote:
> Wait a minute.
>
> Let's step back a bit and think what we want to happen here.
>
> * No GIT_DIR, no --bare. Having GIT_WORK_TREE is an error.
>
> $ mkdir foo && cd foo && git init
>
> We want to say "not bare" and create foo/.git/config and friends.
>
> * No GIT_DIR, with --bare. Having GIT_WORK_TREE is an error.
>
> $ mkdir foo && cd foo && git --bare init
>
> We want to say "is bare" and create foo/config, foo/HEAD and
> friends.
>
> * With GIT_DIR but no GIT_WORK_TREE, with or without --bare.
>
> $ mkdir foo.git && GIT_DIR=foo.git git init
> $ mkdir foo.git && GIT_DIR=foo.git git --bare init
>
> We want to say "is bare" and create foo.git/config and friends.
>
> * With GIT_DIR and GIT_WORK_TREE. Having --bare is an error.
>
> $ mkdir foo.git foo.work
> $ GIT_DIR=foo.git GIT_WORK_TREE=foo.work git init
>
> We want to say "not bare", create foo.git/config and friends,
> and record core.worktree = /full/path/to/foo.work
>
> Is the above list reasonable?
Yes. I'll try to work on it the day after tomorrow.
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-17 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 12:28 git clone regression Junio C Hamano
2007-08-15 16:25 ` [PATCH] Fix initialization of a bare repository Johannes Schindelin
2007-08-15 19:09 ` Junio C Hamano
2007-08-15 19:26 ` Junio C Hamano
2007-08-15 20:41 ` Junio C Hamano
2007-08-17 22:20 ` Johannes Schindelin [this message]
2007-08-27 7:58 ` [PATCH/RFH] " Junio C Hamano
2007-08-27 10:54 ` Johannes Schindelin
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=Pine.LNX.4.64.0708172319480.20400@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).