Elijah Newren <newren@xxxxxxxxx> writes:
>> Pulling without specifying how to reconcile divergent branches is discouraged;
>> you need to specify if you want a merge, a rebase, or a fast-forward.
>> You can squelch this message by running one of the following commands:
>>
>> git config pull.rebase false # merge (the default strategy)
>> git config pull.rebase true # rebase
>> git config pull.ff only # fast-forward only
>>
>> You can replace "git config" with "git config --global" to set a default
>> preference for all repositories.
>> If unsure, run "git pull --merge".
>> Read "git pull --help" for more information.
>>
>> This warning says:
>>
>> 1. There's 3 options: merge, rebase, fast-forward
>> 2. merge is the default strategy
>> 3. If unsure, specify --merge (the default strategy)
>>
>> So taken altogether it does say what is the default strategy.
>
> We don't need to take them together. #2 by itself states the default
> strategy. I don't see why defending #3 as being for the purpose of
> documenting the default strategy is helpful, since it doesn't do that.
Would it work if the line were
If unsure, run "git -c pull.rebase=false pull".
then?
The reason why I bring this up is because the first part only talks
about the choices in the terms of configuration variables, and for
those who are afraid of committing, there is no easy way, unless
they know the "git -c" single-shot mechanism, to "go ahead with one
choice in an experimental basis to see if that is what they want",
and "specify --merge" does not click well with "pull.rebase=false"
that is given in the first part. "git pull --no-rebase" may also
work better than "git pull --merge" from that point of view, though.
But see below.
>> Do you think the crew should disregard the passenger's volition and
>> force him to pay attention to the safety demonstration?
An example that is irrelevant. Passengers who sit on the aisle side
and clutter the floor with their luggages can pose public hazard,
and it is quite sensible for crews to remove them from the plane.
A team member who runs "pull --[no-]rebase" pushes the result, which
may be a new history in a wrong shape, back to the shared repository
probably falls into a different category. ... Or perhaps in the
same public hazard category?
> Useful link there. Based on his comments, we may want to make
> --ff-only, --merge, and --rebase all be mutually exclusive and result
> in an error message if more than one is specified at the command line.
I hope "his comment" does not refer to what I said. Redefining the
semantics of --ff-only (but not --ff=no and friends) to make it
mutually incompatible with merge/rebase was what Felipe wanted to
do, not me.
FWIW, I see the general direction as
- When the history you are pulling is not a descendant of what you
have on your current branch, you must show your preference
between merging their history into yours or rebasing your history
onto theirs.
- In such a case, we error out, with an error message telling them
that they must tell us which one they want in this invocation
(e.g. with "--rebase" or "--no-rebase"). We further tell them
that pull.rebase can be used to record their preference, if they
almost always use the same.
Side note: I earlier said "see below" to refer to this. I
think the message should offer what they can do right now
with command line option first, and then give an option to
configure. IOW, the message quoted in the beginning of this
response gives information in a wrong order. Also,
"discouraged" is misleading, isn't it? When we give this
message, we refuse to proceed until the user specifies.
Another thing to consider is that pull.ff=only (and
--ff-only) may be wrong choice to offer in the error message
quoted above, if one of the objectives is to reduce the
"annoying" message that tells the user that they must
choose. By definition, we do not give the message when our
side do not have our own development, so "I could run 'pull
--ff-only'" is a unusable knowledge to those who see the
message and want to get out of the situation.
- But when the history being pulled is a descendant of the current
branch, and the user does not give us preference between merge
and rebase (either from the command line or with configuration),
there is no need to give such an error message---if you do not
have your own development, we can just fast-forward the current
branch to what we fetched from the other side. This does not
happen with the current system, which is what we want to fix.
- Also when the history from the other side is a descedant and the
user has preference, either to rebase or to merge, either from
the command line or with configuration, we can fast-forward the
current branch to their tip, but there are wrinkles:
. when --ff=no is given and the choice is to merge (not rebase),
we must create an extra merge commit.
. when the choice is to rebase, by definition, rebasing what you
have on top of theirs in this case is the same as fast-forwarding
the current branch to theirs, because "what you have" is an
empty set.
. I am not sure how "pull --rebase --ff=no" should interact if we
don't have our own development. Rebasing our work on top of
theirs is philosophically incompatible with marking where the
side branch begins and ends with an extra commit, so it either
should be rejected when the command line and configuration is
parsed (i.e. regardless of the shape of the history we have at
hand), or --ff=no gets silently ignored when --rebase is given.
I haven't thought this one through.
