From: Junio C Hamano <gitster@pobox•com>
To: Kevin Buckley <Kevin.Buckley@pawsey•org.au>
Cc: git@vger•kernel.org
Subject: Re: Definition of "the Git repository"
Date: Mon, 28 Jun 2021 23:59:21 -0700 [thread overview]
Message-ID: <xmqq4kdhyx4m.fsf@gitster.g> (raw)
In-Reply-To: 7dd55e85-38eb-7346-ff10-7124102cd22b@pawsey.org.au
Kevin Buckley <Kevin.Buckley@pawsey•org.au> writes:
> git init
>
> initialises a Git repository, however, the only thing that changes
> as a result is that a .git directory has been created, ergo, the
> .git directory is the repository.
Well, there is a distinction between "non-bare" and "bare"
repository, so it is not exactly _wrong_ per-se to include the
working tree portion of a non-bare repository as part of the
repository created when you run "git clone", i.e. it is not a crime
to say "please run 'git clone' to get a new repository to work in".
Often we do need to single out the things under .git/ in a non-bare
repository when explaining certain features of Git, and need to
clarify if it is not clear in the context (e.g. "the .git repository
proper in the result of such a non-bare 'git clone'").
It is nothing new in inter-human communication.
If there is a use of word "repository" in our documentation where it
is not clear if the repository proper or the combination of both
working tree and the repository prper is meant, you may want to
propose a clarification patch.
Thanks.
prev parent reply other threads:[~2021-06-29 6:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 1:44 Definition of "the Git repository" Kevin Buckley
2021-06-25 5:56 ` Ævar Arnfjörð Bjarmason
2021-06-25 8:56 ` Igor Djordjevic
2021-06-25 9:14 ` Igor Djordjevic
2021-06-25 19:39 ` Felipe Contreras
2021-06-25 20:48 ` Philip Oakley
2021-06-28 2:24 ` Kevin Buckley
2021-06-28 3:24 ` Felipe Contreras
2021-06-28 4:00 ` Kevin Buckley
2021-06-28 5:21 ` Felipe Contreras
2021-06-29 1:57 ` Kevin Buckley
2021-06-29 2:08 ` Felipe Contreras
2021-06-28 15:18 ` Philip Oakley
2021-06-28 15:34 ` Chris Torek
2021-06-29 6:59 ` Junio C Hamano [this message]
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=xmqq4kdhyx4m.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=Kevin.Buckley@pawsey$(echo .)org.au \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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