Stefan Beller wrote:
> On Wed, Sep 5, 2018 at 4:10 PM Jonathan Nieder <jrnie...@gmail.com> wrote:
>> Broader comment: do you think people will be surprised by this new
>> behavior? Is there anything special we'd need to do to call it out
>> (e.g., print a warning or put something in release notes)?
>
> I guess. Not sure how to approach this best. Maybe we can
> extend the output of 'submodule update' to print that branch names
> instead of hashes for the configured case and keep printing hashes
> only for this case. Although that would not help someone who relies
> on the default solely.
Thinking more out loud: often the simplest migration path involves
multiple steps:
1. Warn in the case that is going to change, with no behavior change
yet.
2. Treat the case that will change as an error. This should
help flush out cases where people were relying on the old behavior.
3. Introduce the new behavior. Warn that old versions of Git don't
support it yet.
4. Eliminate the warning. You're all clear now.
Sometimes some of these steps can be combined.
Another possible approach is to measure. For example, is there some
way to find out how many people are relying in this "git submodule
update --remote" defaulting behavior? One example of this approach is
to make the change (all in one step) in "next" and deploy to some
relevant subpopulation and see if anyone screams. By making the
change in "next" instead of something with more stability guarantees,
you get the ability to roll back quickly.
There are other tools at our disposal --- e.g. command-line flags,
config, other kinds of research.
Here my first instinct would be to say this should be a command-line
flag. To start out, we can keep the historical behavior as a default,
but introduce a command-line option for the new behavior. This way,
people can pass the negation of that command-line option if they want
the older behavior, throughout the transition.
For example (please ignore names):
Step 0: introduce
git submodule update --remote --default-to-master; # current behavior
git submodule update --remote --no-default-to-master; # new behavior
and treat plain "git submodule update --remote" as --default-to-master.
Step 1: when neither --default-to-master nor --no-default-to-master
has been passed, warn when encountering a submodule with no branch
and treat it as "master".
Step 2: when neither --default-to-master nor --no-default-to-master
has been passed, error out when encountering a submodule with no
branch.
Step 3: when neither --default-to-master nor --no-default-to-master
has been passed, warn when encountering a submodule with no branch
and treat it as pinned.
Step 4: eliminate the warning.
What do you think?
Thanks,
Jonathan
