From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v1.8.2-rc0
Date: Mon, 18 Feb 2013 15:09:11 -0800 [thread overview]
Message-ID: <7vobfh8bjc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <vpq4nh9v5an.fsf@grenoble-inp.fr> (Matthieu Moy's message of "Mon, 18 Feb 2013 19:35:28 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Junio C Hamano <gitster@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
Will update.
> 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
> too.
Quite right. Care to do the honors as the proposer to the new
direction?
next prev parent reply other threads:[~2013-02-18 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 0:52 [ANNOUNCE] Git v1.8.2-rc0 Junio C Hamano
2013-02-18 18:35 ` Matthieu Moy
2013-02-18 23:09 ` Junio C Hamano [this message]
2013-02-18 23:59 ` Junio C Hamano
2013-02-19 7:44 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vobfh8bjc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).