Matthieu Moy <matthieu....@grenoble-inp.fr> writes:
> Junio C Hamano <gits...@pobox.com> writes:
>> Git v1.8.2 Release Notes (draft)
>> Backward compatibility notes
>> In the upcoming major release (tentatively called 1.8.2), we will
>> change the behavior of the "git push" command.
>> When "git push [$there]" does not say what to push, we have used the
>> traditional "matching" semantics so far (all your branches were sent
>> to the remote as long as there already are branches of the same name
>> over there). We will use the "simple" semantics
> I don't understand: wasn't this supposed to happen in Git 2.0? Did you
> mean "In the upcoming major release (tentatively called *2.0*)"?
Thanks. I am not sure what I was thinking. Perhaps when we started
this cycle we did want to merge the push-2.0-default-to-simple series
> Also, you may want to mention the argumentless "git add -u" change too.
> It currently has an item below, but this is a future
> backward-incompatible change so it may deserve to appear in this section
Quite right. Care to do the honors as the proposer to the new
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html