Junio C Hamano writes:
> +At Git 2.0 (not *this* one), we
> +plan to change these commands without pathspec to operate on the
> +entire tree, and training your fingers to type "." will protect you
> +against the future change.
My understanding of the plan was more to forbid argumentless git -u|-
Junio C Hamano writes:
>> 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-s
Matthieu Moy writes:
> Junio C Hamano 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" comm
Junio C Hamano 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]"
An early preview Git v1.8.2-rc0 for the upcoming release is now
available for testing at the usual places. The preview includes
contributions from 80+ people, totaling some 570+ no-merge changes
since v1.8.1 and should give you more or less a complete picture of
what the upcoming 1.8.2 would look
5 matches
Mail list logo
