[lkml]   [2013]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ANNOUNCE] Git v1.8.2-rc0
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]" 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*)"?

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

Matthieu Moy

 \ /
  Last update: 2013-02-18 20:01    [W:0.061 / U:0.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site