into the submodule and change branches by hand). The following
extrapolates the “Preferred local submodule branches” series to a
tightly-bound ideal.
Gitlinked commit hash
-
The submodule model revolves around links to commits (“gitlinks”):
$ git ls-tree HEAD
100644 blob
From: W. Trevor King wk...@tremily.us
In another branch of the submodule thread Francesco kicked off, I
mentioned that we could store the preferred local submodule branch on
a per-superbranch level if we used the
.git/modules/submodule-name/config for local overrides [1]. Here's
a patch series
On Tue, Jan 07, 2014 at 10:51:34PM +0100, Francesco Pretto wrote:
2014/1/7 W. Trevor King wk...@tremily.us:
I'd be happy to hear ideas about superproject-branch-specific local
overrides to a hypothetical submodule.name.local-branch, in the
event that a developer doesn't like a default set
On Tue, Jan 07, 2014 at 02:36:25PM -0800, W. Trevor King wrote:
There are three branches that submodule folks usually care about:
1. The linked $sha1 in the superproject (set explicitly for every
superproject commit, and thus for every superproject branch).
2. The remote-tracking
On Wed, Jan 08, 2014 at 03:12:44AM +0100, Francesco Pretto wrote:
2014/1/8 W. Trevor King wk...@tremily.us:
Note that I've moved away from “submodule.name.branch
set means attached” towards “we should set per-superproject-branch
submodule.name.local-branch explicitly” [1].
Honestly, I'm
On Tue, Jan 07, 2014 at 07:47:08PM -0800, W. Trevor King wrote:
#git checkout --recurse-submodules master
( # 'git checkout --recurse-submodules' doesn't exist yet [2,3].
# Even with that patch, 'git checkout' won't respect
# submodule.name.local-branch without further
6 matches
Mail list logo
