git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitry Kakurin" <dmitry.kakurin@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Submodules
Date: Tue, 7 Aug 2007 16:10:38 -0700	[thread overview]
Message-ID: <a1bbc6950708071610g4ea4d874t458cec14a444b519@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708072344450.14781@racer.site>

Yeah, I've already went thru these. But I want (much) more details.
I can ask a bunch of random questions on this list, like:

* Why after 'submodule update' it becomes detached, what if I want it
to stay on certain branch?
* How do I control which branches are fetched?
* What if I do 'commit -a' standing in /super, will /super/submodule
commit as well?
* What if I'm standing in /super/submodule and do 'commit -a'? Will
super notice it in any way?

But I was hoping that it's all summarized somewhere already.

- Dmitry
On 8/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 7 Aug 2007, Dmitry Kakurin wrote:
>
> > Where can I find more information about submodules?
> > I'm interested in both internal implementation details and how to use them.
>
> Most information is found in git-submodule.sh, although
> Documentation/git-submodule.txt has beginnings of a good documentation.
>
> The basic idea is this:
>
> A subdirectory contains a self-contained project.
>
> Once that project is at a stage you want to have in the superproject, you
> can commit that submodule state, much like a subdirectory.
>
> However, the history can progress in much coarser steps for the
> superproject.  IOW an ideal case for msysgit.git, where we want to have a
> stable version which can be checked out with GitMe.
>
> Also, find more about submodules here:
>
> http://git.or.cz/gitwiki/SubprojectSupport?highlight=%28submodule%29
>
> Ciao,
> Dscho

  reply	other threads:[~2007-08-07 23:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 22:37 Submodules Dmitry Kakurin
2007-08-07 22:49 ` Submodules Johannes Schindelin
2007-08-07 23:10   ` Dmitry Kakurin [this message]
2007-08-08 10:27     ` Submodules Sven Verdoolaege
2007-08-07 22:50 ` Submodules Johannes Schindelin
2007-08-07 23:31   ` Submodules Dmitry Kakurin
2007-08-08  0:07     ` Submodules Johannes Schindelin
2007-08-08 10:41     ` Submodules Sven Verdoolaege
2007-08-08 19:33       ` Submodules Junio C Hamano
2007-08-08 19:40         ` Submodules Johannes Schindelin
2007-08-08 19:59           ` Submodules Junio C Hamano
2007-08-08 20:08             ` Submodules Sven Verdoolaege
2007-08-08 22:08               ` Submodules Junio C Hamano
2007-08-08 22:18                 ` Submodules Johannes Schindelin
2007-08-08 20:27             ` Submodules Junio C Hamano
2007-08-08 20:47           ` Submodules Andy Parkins
2007-08-08 21:12             ` Submodules Johannes Schindelin
2007-08-09  5:44               ` Submodules Sven Verdoolaege
2007-08-08 19:53         ` Submodules Sven Verdoolaege
  -- strict thread matches above, loose matches on Subject: below --
2013-05-03 13:45 submodules shawn wilson
2013-05-03 19:51 ` submodules Jens Lehmann
2014-01-23  8:38 submodules shawn wilson
2014-01-23 17:20 ` submodules W. Trevor King

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=a1bbc6950708071610g4ea4d874t458cec14a444b519@mail.gmail.com \
    --to=dmitry.kakurin@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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.
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).