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: Sun, 27 Jun 2021 22:24:59 -0500 [thread overview]
Message-ID: <60d9410bb07a1_aac5d20888@natae.notmuch> (raw)
In-Reply-To: <12dd4f05-456f-c763-441e-5bb16634306a@pawsey.org.au>
Kevin Buckley wrote:
> Everything within the .git directory "belongs", in my way of thinking,
> to the "repository", that is, the directory that gets created when git
> is (init)ialised.
>
> For me, the 'objects", the 'ref/heads', the "staging area' and the like,
> also lie within the repository.
Does it?
Suppose you have three directories, each with exactly the same contents
in their corresponding .git directory, the only difference is the
.git/index file:
a) No .git/index file at all
b) The .git/index file doesn't have anything staged
c) The .git/index file contains some staged changes
Do you really consider them three different repositories?
In my mind the staging area is where you put stuff in preparation for
the commit. The commit is part of the repository, the staging area
isn't.
--
Felipe Contreras
next prev parent reply other threads:[~2021-06-28 3:25 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 [this message]
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
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=60d9410bb07a1_aac5d20888@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).