From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Thomas Ackermann <th.acker@arcor.de>,
git@vger.kernel.org, davvid@gmail.com,
Lars Hjemli <hjemli@gmail.com>,
Jens Lehmann <Jens.Lehmann@web.de>,
Fredrik Gustafsson <iveqy@iveqy.com>
Subject: Re: [PATCH 5/6] Add a description for 'gitfile' to glossary
Date: Fri, 1 Feb 2013 11:46:37 -0800 [thread overview]
Message-ID: <20130201194637.GD12368@google.com> (raw)
In-Reply-To: <7vlib7al90.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> How about saying something like this here in the glossary:
>
> A plain file `.git` at the root of a working tree that
> points at the directory that is the real repository.
>
> And then as a separate patch, in gitrepository-layout.txt (eek---see
> the other thread), we can do something like this:
>
> Documentation/gitrepository-layout.txt | 24 ++++++++++++++++++------
> 1 file changed, 18 insertions(+), 6 deletions(-)
Looks correct and very readable. Thanks.
Jonathan
(patch left unsnipped for reference)
> diff --git a/Documentation/gitrepository-layout.txt b/Documentation/gitrepository-layout.txt
> index 9f62886..473c6a0 100644
> --- a/Documentation/gitrepository-layout.txt
> +++ b/Documentation/gitrepository-layout.txt
> @@ -12,12 +12,24 @@ $GIT_DIR/*
> DESCRIPTION
> -----------
>
> -You may find these things in your git repository (`.git`
> -directory for a repository associated with your working tree, or
> -`<project>.git` directory for a public 'bare' repository. It is
> -also possible to have a working tree where `.git` is a plain
> -ASCII file containing `gitdir: <path>`, i.e. the path to the
> -real git repository).
> +A Git repository comes in two different flavours:
> +
> + * a `.git` directory at the root of the working tree;
> +
> + * a `<project>.git` directory that is a 'bare' repository
> + (i.e. without its own working tree), that is typically used for
> + exchanging histories with others by pushing into it and fetching
> + from it.
> +
> +*Note*: Also you can have a plain text file `.git` at the root of
> +your working tree, containing `gitdir: <path>` to point at the real
> +directory that has the repository. This mechanism is often used for
> +a working tree of a submodule checkout, to allow you in the
> +containing superproject to `git checkout` a branch that does not
> +have the submodule. The `checkout` has to remove the entire
> +submodule working tree, without losing the submodule repository.
> +
> +These things may exist in a Git repository.
>
> objects::
> Object store associated with this repository. Usually
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-02-01 19:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 20:16 Aw: Re: [PATCH 1/2] Change old system name 'GIT' to 'Git' Thomas Ackermann
2013-01-20 21:08 ` Junio C Hamano
2013-01-21 18:36 ` [PATCH v2 0/6] GIT, Git, git Thomas Ackermann
2013-01-21 19:56 ` Junio C Hamano
2013-01-21 20:01 ` Junio C Hamano
2013-01-21 18:38 ` [PATCH v2 1/6] Change old system name 'GIT' to 'Git' Thomas Ackermann
2013-01-21 18:40 ` [PATCH v2 2/6] Change 'git' to 'Git' whenever the whole system is referred to #1 Thomas Ackermann
2013-01-21 18:51 ` Aw: [PATCH v2 0/6] GIT, Git, git Thomas Ackermann
2013-01-21 19:12 ` [PATCH v3 " Thomas Ackermann
2013-01-21 19:16 ` [PATCH v3 1/6] Change old system name 'GIT' to 'Git' Thomas Ackermann
2013-01-22 0:39 ` Junio C Hamano
2013-01-22 9:44 ` Aw: " Thomas Ackermann
2013-01-22 16:45 ` Junio C Hamano
2013-01-21 19:17 ` [PATCH v3 2/6] Change 'git' to 'Git' whenever the whole system is referred to #1 Thomas Ackermann
2013-01-22 0:41 ` Junio C Hamano
2013-01-22 23:48 ` Junio C Hamano
2013-01-23 0:19 ` Junio C Hamano
2013-01-23 2:24 ` Junio C Hamano
2013-01-23 2:32 ` Junio C Hamano
2013-01-21 19:19 ` [PATCH v3 3/6] Change 'git' to 'Git' whenever the whole system is referred to #2 Thomas Ackermann
2013-01-23 0:53 ` Junio C Hamano
2013-01-23 2:48 ` Junio C Hamano
2013-01-23 3:44 ` David Aguilar
2013-01-23 4:17 ` Junio C Hamano
2013-01-23 8:58 ` Aw: " Thomas Ackermann
2013-02-01 0:46 ` Junio C Hamano
2013-02-01 18:04 ` Aw: " Thomas Ackermann
2013-02-01 18:37 ` Junio C Hamano
2013-02-01 18:06 ` [PATCH 1/6] fixup! fixup! " Thomas Ackermann
2013-02-01 18:07 ` [PATCH 2/6] fixup! fixup! fixup! Change 'git' to 'Git' whenever the whole system is referred to #1 Thomas Ackermann
2013-02-01 19:43 ` Jonathan Nieder
2013-02-01 20:16 ` Junio C Hamano
2013-02-01 18:08 ` [PATCH 3/6] fixup! Documentation: avoid poor-man's small caps Thomas Ackermann
2013-02-01 18:44 ` Junio C Hamano
2013-02-01 18:10 ` [PATCH 4/6] Fix places where 'Git' should be 'git Thomas Ackermann
2013-02-01 18:11 ` [PATCH 5/6] Add a description for 'gitfile' to glossary Thomas Ackermann
2013-02-01 18:41 ` Junio C Hamano
2013-02-01 19:26 ` Junio C Hamano
2013-02-01 19:46 ` Jonathan Nieder [this message]
2013-02-01 18:12 ` [PATCH 6/6] Use consistent links for User Manual and Everyday Git; Fix a quoting error Thomas Ackermann
2013-02-01 18:43 ` Junio C Hamano
2013-02-01 19:51 ` Jonathan Nieder
2013-02-01 20:17 ` Junio C Hamano
2013-02-01 20:25 ` Aw: " Thomas Ackermann
2013-01-21 19:21 ` [PATCH v3 4/6] Change 'git' to 'Git' whenever the whole system is referred to #3 Thomas Ackermann
2013-01-23 2:49 ` Junio C Hamano
2013-01-21 19:22 ` [PATCH v3 5/6] Change 'git' to 'Git' whenever the whole system is referred to #4 Thomas Ackermann
2013-01-23 3:16 ` Junio C Hamano
2013-01-21 19:24 ` [PATCH v3 6/6] Add rule for when to use 'git' and when to use 'Git' Thomas Ackermann
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=20130201194637.GD12368@google.com \
--to=jrnieder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hjemli@gmail.com \
--cc=iveqy@iveqy.com \
--cc=th.acker@arcor.de \
/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).