From: Daniel Barkalow <barkalow@iabervon.org>
Date: Tue, 28 Nov 2006 21:32:21 GMT
Subject: Re: [RFC] Submodules in GIT
Message-ID: <Pine.LNX.4.64.0611281614450.20138@iabervon.org>
In-Reply-To: <20061128211012.GJ28337@spearce.org>

On Tue, 28 Nov 2006, Shawn Pearce wrote:

> Daniel Barkalow <barkalow@iabervon.org> wrote:
> > and then it makes sense to let you do multiple commits with a single 
> > command when the paths end in different modules, since that's obviously 
> > what you're requesting, and then -a must do all of them.
> 
> Except what if the submodules have different commit message
> standards?  E.g. one requires signoff and another doesn't?  Or one
> allows privately held information (e.g. its your coporate project)
> and one doesn't (e.g. its an open source project you use/contribute
> to)?

I don't think you'd ever want the same commit message for commits in two 
projects. In any case where you'd commit a submodule in the process of 
committing a supermodule, git would do this by recursively calling 
git-commit, which would prompt for separate commit messages.

	-Daniel