Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: "skillzero@gmail.com" <skillzero@gmail.com>, git@vger.kernel.org
Subject: Re: Why do git submodules require manual checkouts and commits?
Date: Fri, 16 May 2008 14:58:21 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0805161457250.30431@racer> (raw)
In-Reply-To: <32541b130805160643y3bfe609et22b2d00627f98c04@mail.gmail.com>

Hi,

On Fri, 16 May 2008, Avery Pennarun wrote:

> So I think it would be very bad if the supermodule automatically
> updated to the latest version of the submodule whenever you commit in
> the submodule.  *However*, the other way around might be fine: if you
> commit in the supermodule, maybe it should commit in the submodule at
> the same time and link to that specific commit.  I'm pretty sure that
> idea doesn't have any *fundamental* flaws, it's just got a lot of
> really tricky details that need to be worked out.

Just the fundamental flaw that you might _not_ want to commit that, just 
as you can have a dirty Makefile _forever_.

Ciao,
Dscho

  reply	other threads:[~2008-05-16 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16  4:16 Why do git submodules require manual checkouts and commits? skillzero
2008-05-16 10:17 ` Johannes Schindelin
2008-05-16 13:43 ` Avery Pennarun
2008-05-16 13:58   ` Johannes Schindelin [this message]
2008-05-16 14:12     ` Avery Pennarun
2008-05-16 14:24       ` Johannes Schindelin
2008-05-16 14:44         ` Avery Pennarun
2008-05-16 14:58         ` Lars Hjemli
2008-05-19  4:38   ` skillzero

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=alpine.DEB.1.00.0805161457250.30431@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=skillzero@gmail.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