On 14 November 2017 at 13:23, Jacob Keller <jacob....@gmail.com
> I work with a team that uses submodules fairly heavily, and a few of our
> developers have grown accustomed to stacked git. Unfortunately, there are a
> few problems with stacked git, when it comes to submodules.
> The first major pain point is that "stg refresh" will include submodule
> pointer updates by default. This can cause issues if users who are new to
> submodules, when an environment expects rapidly changing submodules (such as
> our use case).
> Since this leads to accidental commits of the submodule pointer, I am
> proposing a patch to stacked git, which causes "stg refresh" to simply
> exclude submodules by default, unless either (a) stgit.refreshsubmodules is
> "yes", (b) the --submodules command line argument is given, or (c) the
> submodule is included in the list of paths to update.
> This ensures that in general submodules will not be "refreshed" (since they
> are often accidentally out of date due to the way that git detects
> differences of submodules) but if necessary, users are able to easily
> include the submodules to patches via 3 easy mechanisms, depending on the
> users preference and work flow.
Yeah, I run into this problem a lot. I can't help feeling that stgit