git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2020, #02; Mon, 10)
Date: Tue, 11 Aug 2020 12:24:26 -0700	[thread overview]
Message-ID: <xmqq364t9ead.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAPig+cRtS3iMp3zLRKBOvEchrDPrCmozndbFpWtjiosk5nqGew@mail.gmail.com> (Eric Sunshine's message of "Tue, 11 Aug 2020 01:01:27 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Mon, Aug 10, 2020 at 3:45 PM Junio C Hamano <gitster@pobox.com> wrote:
>> * es/init-no-separate-git-dir-in-bare (2020-08-10) 1 commit
>> - init: disallow --separate-git-dir with bare repository
>>
>> "git init --separate-git-dir" can be used in an existing repository
>> with a working tree to move its .git/ directory away from the
>> working tree. Even though this re-init feature makes no sense in
>> an existing bare repository, it was not erroring out. Now it does.
>
> This description is a bit misleading since it focuses only on existing
> repositories, however, --separate-git-dir is intended for use with
> both new and existing repositories. So, perhaps the description could
> be rewritten something like this:
>
>     The purpose of "git init --separate-git-dir" is to initialize a
>     new project with the repository separate from the working tree,
>     or, in the case of an existing project, to move the repository
>     (the .git/ directory) out of the working tree. It does not make
>     sense to use --separate-git-dir with a bare repository for which
>     there is no working tree, so disallow its use with bare
>     repositories.

Thanks.

  reply	other threads:[~2020-08-11 19:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 19:44 What's cooking in git.git (Aug 2020, #02; Mon, 10) Junio C Hamano
2020-08-11  5:01 ` Eric Sunshine
2020-08-11 19:24   ` Junio C Hamano [this message]
2020-08-11  6:53 ` Jeff King
2020-08-11  9:33   ` Patrick Steinhardt
2020-08-11  9:59   ` brian m. carlson
2020-08-11 10:10 ` Sergey Organov
2020-08-11 19:23   ` Junio C Hamano
2020-08-11 19:34     ` Sergey Organov
2020-08-11 20:17       ` Sergey Organov
2020-08-11 21:36         ` Junio C Hamano
2020-08-12  8:15           ` Sergey Organov
2020-08-11 20:28       ` Junio C Hamano
2020-08-11 21:26         ` Sergey Organov
2020-08-11 22:12           ` Junio C Hamano
2020-08-11 13:48 ` Taylor Blau
2020-08-11 14:27 ` Matheus Tavares Bernardino
2020-08-11 19:20   ` Junio C Hamano

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=xmqq364t9ead.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.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).