On Mon, Apr 29, 2013 at 3:15 PM, Marc Branchaud <marcnarc@xxxxxxxxxxx> wrote: > --- a/Documentation/RelNotes/1.8.3.txt > +++ b/Documentation/RelNotes/1.8.3.txt > @@ -8,23 +8,22 @@ 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). In Git 2.0, the default will change to the "simple" > -semantics that pushes the current branch to the branch with the same > -name, only when the current branch is set to integrate with that > -remote branch. There is a user preference configuration variable > +semantics that pushes only the current branch to the branch with the same > +name, and only when the current branch is set to integrate with that > +remote branch. Use the user preference configuration variable > "push.default" to change this. If you are an old-timer who is used > -to the "matching" semantics, you can set it to "matching" to keep the > +to the "matching" semantics, you can set the varaible to "matching" to keep the s/varaible/variable/ > traditional behaviour. If you want to live in the future early, > you can set it to "simple" today without waiting for Git 2.0. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html