Git development
 help / color / mirror / Atom feed
From: Sergei Organov <osv@javad.com>
To: Steven Grimm <koreth@midwinter.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
	Finn Arne Gangstad <finnag@pvv.org>,
	git@vger.kernel.org
Subject: Re: Partial checkouts / submodules
Date: Tue, 20 Nov 2007 21:55:28 +0300	[thread overview]
Message-ID: <87ir3wzqzj.fsf@osv.gnss.ru> (raw)
In-Reply-To: <1AD9B065-647B-4672-B6B0-8D4447960913@midwinter.com> (Steven Grimm's message of "Tue\, 20 Nov 2007 10\:26\:43 -0800")

Steven Grimm <koreth@midwinter.com> writes:

> On Nov 20, 2007, at 10:03 AM, Daniel Barkalow wrote:
>> This has theoretical problems: it's going to be practically
>> impossible, in
>> most cases, to write a commit message that describes changes in three
>> submodules (which are sometimes used in the context of a different
>> supermodule) as well as the supermodule.
>
> I got the impression from his email that there *are* no other
> supermodules. The submodules are submodules purely to reduce the
> amount of data people have to transfer around, not because they're
> logically distinct from the parent.

I got the same impression, and then I wonder if the next logical thing
the OP will need is, say, support for content moves between
submodules. Somehow I doubt git will ever support that.

-- 
Sergei.

  parent reply	other threads:[~2007-11-20 18:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 15:59 Partial checkouts / submodules Finn Arne Gangstad
2007-11-20 17:33 ` Sven Verdoolaege
2007-11-20 18:19   ` Finn Arne Gangstad
2007-11-20 18:42     ` Sven Verdoolaege
2007-11-20 18:59     ` Daniel Barkalow
2007-11-20 19:22       ` Finn Arne Gangstad
2007-11-20 20:18         ` Daniel Barkalow
2007-11-21  0:04     ` Jakub Narebski
2007-11-20 18:03 ` Daniel Barkalow
2007-11-20 18:26   ` Steven Grimm
2007-11-20 18:36     ` Daniel Barkalow
2007-11-20 18:55     ` Sergei Organov [this message]
2007-11-20 19:15       ` Daniel Barkalow

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=87ir3wzqzj.fsf@osv.gnss.ru \
    --to=osv@javad.com \
    --cc=barkalow@iabervon.org \
    --cc=finnag@pvv.org \
    --cc=git@vger.kernel.org \
    --cc=koreth@midwinter.com \
    /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