From: Junio C Hamano <gitster@pobox•com>
To: Andrew Keller <andrew@kellerfarm•com>
Cc: Henri GEIST <geist.henri@laposte•net>,
Git List <git@vger•kernel.org>,
Jens Lehmann <Jens.Lehmann@web•de>
Subject: Re: [PATCH/RFC] Documentation: Say that submodule clones use a separate gitdirs.
Date: Fri, 07 Mar 2014 14:19:12 -0800 [thread overview]
Message-ID: <xmqqzjl1slcv.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <BEB30FB8-204C-4272-8F94-6210D96FB2CB@kellerfarm.com> (Andrew Keller's message of "Fri, 7 Mar 2014 16:42:44 -0500")
Andrew Keller <andrew@kellerfarm•com> writes:
>> diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
>> index 21cb59a..ea837fd 100644
>> --- a/Documentation/git-submodule.txt
>> +++ b/Documentation/git-submodule.txt
> ...
> Also, this file contains mostly high-level documentation, and this
> addition feels technical in nature. Is there a location for more
> technical documentation? Or, perhaps it can be reworded to sound
> less technical?
I tend to agree that the new paragraph looked somewhat out of place
and goes into a too low-level detail of the implementation.
The repository-layout documentation may be a better place for
readers to learn what lives where inside $GIT_DIR.
next prev parent reply other threads:[~2014-03-07 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 7:53 [PATCH/RFC] Documentation: Say that submodule clones use a separate gitdirs Henri GEIST
2014-03-07 21:42 ` Andrew Keller
2014-03-07 22:19 ` Junio C Hamano [this message]
2014-03-07 22:35 ` Henri GEIST
2014-03-07 23:37 ` Junio C Hamano
2014-03-08 0:50 ` Henri GEIST
2014-03-09 23:24 ` Andrew Keller
2014-03-10 7:52 ` Henri GEIST
2014-03-10 15:31 ` Junio C Hamano
2014-03-10 18:22 ` Henri GEIST
2014-03-10 19:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzjl1slcv.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Jens.Lehmann@web$(echo .)de \
--cc=andrew@kellerfarm$(echo .)com \
--cc=geist.henri@laposte$(echo .)net \
--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