git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Kevin Buckley <Kevin.Buckley@pawsey.org.au>, git@vger.kernel.org
Subject: Re: Definition of "the Git repository"
Date: Mon, 28 Jun 2021 21:08:39 -0500	[thread overview]
Message-ID: <60da80a7d0abb_20757208c5@natae.notmuch> (raw)
In-Reply-To: <a5579940-237b-2e4d-bf18-bc0a8f2f1ee3@pawsey.org.au>

Kevin Buckley wrote:
> On 2021/06/28 13:21, Felipe Contreras wrote:
> > 
> > To try to make it more orthogonal, let's suppose the index file was
> > outside the .git directory. Would you consider then the staging area
> > separate from the repository?
> > 
> > In fact, we don't have to suppose:
> > 
> >    GIT_INDEX_FILE=/tmp/index git checkout @~ -- .
> > 
> > Does that command change the repository in any way?
>   
> I have to admit that I don't know, and that I can't immediately
> see where the "repository" would be, in that example. This is
> obviously a gap in my understanding: happy to defer to yours.

Well, think about it.

> I do however feel that the fact that we have moved to using examples
> that override the Git Index file on the command line, in order to
> define what a "repository" is, just so that we might be able to give
> a "more correct" definition of the term, to someone completely new to
> Git, suggests that, as others have already noted in the discussion,
> it's not easy to be "correct"?

No. The repository is what the repository is. The command is merely an
aid for *you* to think about it.

If you are trying to define what a swan is, and you think a swan is a
white bird, but then I show you a black swan, what do you think you
should do with your definition?

What's complicated about this definition?

  A git repository is contained in the .git directory, but it's not the
  same thing. The staging area is usually inside the .git directory too,
  but it's not part of the repository.

Why do you want to make it more complicated than that?

-- 
Felipe Contreras

  reply	other threads:[~2021-06-29  2:08 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 [this message]
2021-06-28 15:18     ` Philip Oakley
2021-06-28 15:34       ` Chris Torek
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=60da80a7d0abb_20757208c5@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=Kevin.Buckley@pawsey.org.au \
    --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.
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).