Am 17.04.2014 21:23, schrieb Junio C Hamano:
> "W. Trevor King" <> writes:
>> There have been a number of submodule series in
>> flight recently, and I'm having trouble keeping track of them all ;).
> Unfortunately I share that same feeling X-<.
> Could you guys collectively summarize what issues each of these
> in-flight topics try to address and how, how close it is to achieve
> concensus, and how it interact with other proposed topics?

I'm aware of these topics:

- My 4 "Never ignore staged but ignored submodules" patches

  I recall that everyone agreed that this is a good change.

- Johan's "Test various 'git submodule update' scenarios"

  Intended to document current behavior of the submodule.<name>.branch
  setting (and others) as a starting point for a discussion of how
  that could (and should) evolve. Needs some cooking.

- My "submodule test harness" RFC series (currently 14 patches)

  Similar to Johan's patch I try to document the current behavior
  of Git, but with the focus on all work tree manipulating commands
  (not only 'submodule update' handling all submodule changes. Will
  send to the list again when I resolved the last outstanding issues,
  current state can be seen in the submodule-test-harness branch of
  my GitHub repo. My next to-be-finished topic.

- Ronald's two "Teach add and commit the --ignore-submodules option"

  Will review v4 soonish, looking good from the first cursory look.

- My "recursive submodule checkout" series

  Needs to be rerolled, I intend to extend my "submodule test harness"
  to cover all relevant scenarios for this series.

- Heiko's "config cache for submodules" patch

  Needed for my recursive checkout series to populate new submodules.

And then a not yet surfaced "do not replace submodules with a file"
fix I intend to send between the "submodule test harness" and the
"recursive submodule checkout" series.

Hope that makes it clearer ;-)
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to