From: Chris Torek <chris.torek@gmail.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: Kevin Buckley <Kevin.Buckley@pawsey.org.au>,
Git List <git@vger.kernel.org>
Subject: Re: Definition of "the Git repository"
Date: Mon, 28 Jun 2021 08:34:58 -0700 [thread overview]
Message-ID: <CAPx1Gvcu9XzZF_LbV8YFsiGhL1DPwki-BNp5-5ZeB9BeiRj1AQ@mail.gmail.com> (raw)
In-Reply-To: <070e36dc-f126-661a-3af7-b44d47ef7861@iee.email>
On Mon, Jun 28, 2021 at 8:24 AM Philip Oakley <philipoakley@iee.email> wrote:
> My main point was that there is this creative tension between the
> different contexts and that beginners should be aware that it's not all
> cut and dried in the same way that language definitions tend to be.
Users should be aware that users are humans, and humans are
not consistent. Nothing is as cut-and-dried as it might appear, ever. Or,
as Kant put it: "Out of the crooked timber of humanity, no straight thing
was ever made." https://en.wikipedia.org/wiki/Crooked_Timber
(If you want to put fine distinctions on things, some parts of a repository
are repository-wide, and some parts are work-tree-specific. The git
worktree command, when it adds a new work-tree, adds a new index
and HEAD and *_HEAD and other work-tree-specific refs, for instance.
That said, I still teach that .git mainly contains the repository proper,
with the rest being your working tree -- or, once we introduce git worktree,
your *main* working tree.)
Chris
next prev parent reply other threads:[~2021-06-28 15:51 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 [this message]
2021-06-29 6:59 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPx1Gvcu9XzZF_LbV8YFsiGhL1DPwki-BNp5-5ZeB9BeiRj1AQ@mail.gmail.com \
--to=chris.torek@gmail.com \
--cc=Kevin.Buckley@pawsey.org.au \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.email \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).