From: "Santi Béjar" <santi@agolina.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Finn Arne Gangstad <finnag@pvv.org>, git@vger.kernel.org
Subject: Re: [PATCH 4/4] Rename push.default to push.style
Date: Mon, 30 Mar 2009 11:07:10 +0200 [thread overview]
Message-ID: <adf1fd3d0903300207j479b6e91gc6ed00695a00e157@mail.gmail.com> (raw)
In-Reply-To: <adf1fd3d0903300200v65393b1bif0050392aa44652e@mail.gmail.com>
2009/3/30 Santi Béjar <santi@agolina.net>:
> 2009/3/30 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>> On Mon, 30 Mar 2009, Finn Arne Gangstad wrote:
>>> Some people may have started setting push.default already, so changing
>>> the name may cause additional grief.
>>
>> ... indeed, it is too late now. The milk has boiled already.
>
> I have it configured, but I think we can fix these type of things
> while they are in 'next'.
>
Now that I've recheck it, it seems to be in 'master', it's less clear,
but I still think we can fix these type of things while they are not
in a relased version.
The people with that setting is following the development version, and
can easily notice/change it.
Santi
next prev parent reply other threads:[~2009-03-30 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 23:10 [PATCH 0/4] push.default and branch.<name>.{remote,merge} changes Santi Béjar
2009-03-28 23:10 ` [PATCH 1/4] Documentation: enhance branch.<name>.{remote,merge} Santi Béjar
2009-03-29 1:38 ` Jay Soffian
2009-03-29 10:54 ` Santi Béjar
2009-03-28 23:10 ` [PATCH 2/4] Documentation: push.default applies to all remotes Santi Béjar
2009-03-28 23:10 ` [PATCH 3/4] Documentation: branch.*.merge can also afect 'git-push' Santi Béjar
2009-03-28 23:10 ` [PATCH 4/4] Rename push.default to push.style Santi Béjar
2009-03-30 8:01 ` Finn Arne Gangstad
2009-03-30 8:23 ` Johannes Schindelin
2009-03-30 9:00 ` Santi Béjar
2009-03-30 9:07 ` Santi Béjar [this message]
2009-03-30 10:29 ` Jeff King
2009-03-30 12:50 ` Santi Béjar
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=adf1fd3d0903300207j479b6e91gc6ed00695a00e157@mail.gmail.com \
--to=santi@agolina.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=finnag@pvv.org \
--cc=git@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).