From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 00/10] push: switch default from "matching" to "simple"
Date: Sat, 05 Jan 2013 20:39:55 +0100 [thread overview]
Message-ID: <vpqpq1ja06s.fsf@grenoble-inp.fr> (raw)
In-Reply-To: <1357368788-28035-1-git-send-email-gitster@pobox.com> (Junio C. Hamano's message of "Fri, 4 Jan 2013 22:52:58 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> We promised to change the behaviour of lazy "git push [there]" that
> does not say what to push on the command line from "matching" to
> "simple" in Git 2.0. Even though the top-level RelNotes symbolic
> link points at 1.8.2, we can change our mind to tag 2.0 at the end
> of this cycle.
I had a quick look at the series, it sounds straightforward and correct.
Thanks,
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-01-05 19:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 6:52 [PATCH 00/10] push: switch default from "matching" to "simple" Junio C Hamano
2013-01-05 6:52 ` [PATCH 01/10] t5404: do not assume the "matching" push is the default Junio C Hamano
2013-01-05 6:53 ` [PATCH 02/10] t5505: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 03/10] t5516: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 04/10] t5517: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 05/10] t5519: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 06/10] t5531: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 07/10] t7406: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 08/10] t9400: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 09/10] t9401: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 10/10] push: switch default from "matching" to "simple" Junio C Hamano
2013-01-05 19:39 ` Matthieu Moy [this message]
2013-01-08 22:28 ` [PATCH 11/10] doc: push.default is no longer "matching" Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqpq1ja06s.fsf@grenoble-inp.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).