git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Further clarify the description
Date: Thu, 17 Jul 2008 16:37:29 +0300	[thread overview]
Message-ID: <20080717133729.GF4379@zakalwe.fi> (raw)
In-Reply-To: <20080717122911.32334.73465.stgit@localhost>

On Thu, Jul 17, 2008 at 02:29:20PM +0200, Petr Baudis wrote:
> +Submodules allow foreign repositories to be embedded within a dedicated
> +subdirectory of the source tree, always pointed at a particular commit.
> +They are not to be confused with remotes, which are meant mainly for branches
> +of the same project; submodules are meant for different projects you would like
> +to make part of your source tree, while the history of the two projects still
> +stays completely independent and you cannot modify the contents of the
> +submodule from within the main project.

That is nice, thanks!

-- 
Heikki Orsila
heikki.orsila@iki.fi
http://www.iki.fi/shd

  reply	other threads:[~2008-07-17 13: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
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 [this message]
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=20080717133729.GF4379@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).