On 11-12-12 05:56 PM, Phil Hord wrote:
> On Mon, Dec 12, 2011 at 2:13 PM, Leif Gruenwoldt <leifer@xxxxxxxxx> wrote:
>> On Mon, Dec 12, 2011 at 1:42 PM, Andreas T.Auer
>> <andreas.t.auer_gtml_37453@xxxxxxxxxxxx> wrote:
>>
>>> The next question is: Wouldn't you like to have the new stable branch only
>>> pulled in, when the projectX (as the superproject) is currently on that new
>>> development branch (maybe master)?
>>>
>>> But if you checkout that fixed released version 1.2.9.8, wouldn't it be
>>> better that in that case the gitlinked version of the submodule is checked
>>> out instead of some unrelated new version? I mean, when the gitlinks are
>>> tracked with the projectX commits, this should work well.
>>>
>>> And what about a maintenance branch, which is not a fixed version but a
>>> quite stable branch which should only have bugfixes. Shouldn't the auto-pull
>>> be disabled in that case, too?
>>>
>>> I think the "auto-pull" behavior should depend on the currently checked out
>>> branch. So the configuration options should allow the definition of one or
>>> more mappings.
>>
>> Yes. I think you nailed it. The floating behaviour would best be
>> configured per branch.
>
> Yes, I think you nailed it too. I've been thinking the same thing for
> a while now, but I didn't know how to express it completely. Some of
> the discussion on here last week gelled the last bits in my mind.
>
> To wit, I think I would want something like this in my project:
>
> Use gitlinks when the superproject HEAD is one of these:
> refs/heads/maint/*
> refs/heads/svn/* (historic branches)
> refs/tags/*
> <SHA1> (detached)
>
> Float on the rest, using the branch given in .gitmodules (which may be
> * to mean "use the same branch as the superproject".)
>
> But maybe it is foolish of me to keep branches where I really want
> lightweight tags. If so, I could get away with this:
>
> Float if .git/HEAD begins with "refs/heads"
> Else, use the SHA1.
Wouldn't this break creating a bugfix topic branch based on an earlier
revision of the repo? I wouldn't want such a branch to automatically give me
the latest submodules.
I'd prefer to have floating be explicitly configured on a per-branch (or
per-branch-glob) basis. So in addition to what Jens described yesterday [1]
to configure an individual submodule's floating branch, I suggest there also
be a new section in the .gitmodules file for configuring the super-repo's
floating branches, e.g.
[super]
floaters = refs/heads/master refs/heads/dev*
[submodule "Sub1"]
path = foo/bar
branch = maint
url = ...
[submodule "Sub2"]
path = other/place
url = ...
This would mean that whenever the super-repo checks out either the "master"
branch or a branch whose name starts with "dev" (assuming recursive checkouts
are on):
* The Sub1 submodule automatically checks out the tip of its
"maint" branch.
* The Sub2 submodule (lacking a "branch" variable) would not float
and would check out the commit recorded in the super-repo.
A super-repo recursive-checkout that doesn't match a floaters pattern would
work in the regular, non-floating way.
M.
[1] http://article.gmane.org/gmane.comp.version-control.git/186969
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html