From: Heikki Orsila <shdl@zakalwe.fi>
To: Petr Baudis <pasky@suse.cz>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-submodule.txt: Add Description section
Date: Tue, 15 Jul 2008 21:37:05 +0300 [thread overview]
Message-ID: <20080715183705.GD4379@zakalwe.fi> (raw)
In-Reply-To: <20080715102119.26321.78530.stgit@localhost>
On Tue, Jul 15, 2008 at 12:22:07PM +0200, Petr Baudis wrote:
> +Submodules are a special kind of tree entries which do not refer to a blob or
> +a directory, but to a particular tree in another repository (living at a given
> +URL).
Better to say what a submodule is, rather than what it isn't:
"Submodules are a special kind of tree entries which refer to a
particular tree in another repository ..."
Also, I think you should make the following explicit:
"A submodule is visible as subdirectory in the working directory.
However, the submodule is not part of the main repository.
This is a differene to "remotes". In remotes only the contents of
other repositories is tracked, but their content is not visible in the
working directory."
--
Heikki Orsila
heikki.orsila@iki.fi
http://www.iki.fi/shd
next prev parent reply other threads:[~2008-07-15 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 10:22 [PATCH] Documentation/git-submodule.txt: Add Description section Petr Baudis
2008-07-15 14:06 ` Junio C Hamano
2008-07-15 18:37 ` Heikki Orsila [this message]
2008-07-16 18:44 ` [PATCHv2] " Petr Baudis
2008-07-16 19:15 ` Kalle Olavi Niemitalo
2008-07-16 19:29 ` Junio C Hamano
2008-07-17 12:18 ` Petr Baudis
2008-07-17 12:29 ` [PATCH] Documentation/git-submodule.txt: Further clarify the description Petr Baudis
2008-07-17 13:37 ` Heikki Orsila
2008-07-17 20:24 ` Junio C Hamano
2008-07-18 13:36 ` Petr Baudis
2008-07-18 13:40 ` Petr Baudis
2008-07-17 10:41 ` [PATCHv2] Documentation/git-submodule.txt: Add Description section Heikki Orsila
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=20080715183705.GD4379@zakalwe.fi \
--to=shdl@zakalwe.fi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
/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).