From: "Santi Béjar" <santi@agolina.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCHv2 4/4] Rename push.default to push.mode
Date: Mon, 30 Mar 2009 14:37:52 +0200 [thread overview]
Message-ID: <adf1fd3d0903300537i41d4aef3g49ab6bde9343cbc5@mail.gmail.com> (raw)
In-Reply-To: <49D0A1FE.60300@drmicha.warpmail.net>
2009/3/30 Michael J Gruber <git@drmicha.warpmail.net>:
> Santi Béjar venit, vidit, dixit 30.03.2009 12:11:
>> push.default was too generic, and also didn't specify if it was about
>> remote, refspec, branches, behaviour...
>
> I guess we go for US spelling here, so it's "behavior" ;)
Ok.
>> diff --git a/Documentation/config.txt b/Documentation/config.txt
>> index 38ab785..80bb3a6 100644
>> --- a/Documentation/config.txt
>> +++ b/Documentation/config.txt
>> @@ -480,7 +480,7 @@ branch.<name>.remote::
>> branch.<name>.merge::
>> It defines, together with branch.<name>.remote, the upstream branch
>> for the given branch. It tells 'git-fetch'/'git-pull' which
>> - branch to merge and can also afect 'git-push' (see push.default).
>> + branch to merge and can also afect 'git-push' (see push.mode).
>
> s/afect/affect/
>
OK
>
> Your patches contain quoted-printable characters all over the place.
I don't see the quoted-printable characters, I see them in utf-8 and 8bit.
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Maybe some server in between is recoding it.
> Are
> they not sent with git send-email?
They are send with git send-email and msmtp.
Santi
next prev parent reply other threads:[~2009-03-30 12:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 10:11 [PATCHv2 0/4] push.default and branch.<name>.{remote,merge} changes Santi Béjar
2009-03-30 10:11 ` [PATCHv2 1/4] Documentation: enhance branch.<name>.{remote,merge} Santi Béjar
2009-03-30 10:11 ` [PATCHv2 2/4] Documentation: push.default applies to all remotes Santi Béjar
2009-03-30 10:11 ` [PATCHv2 3/4] Documentation: branch.*.merge can also afect 'git-push' Santi Béjar
2009-03-30 10:35 ` Michael J Gruber
2009-03-30 16:47 ` Junio C Hamano
2009-03-30 22:06 ` Santi Béjar
2009-04-02 6:08 ` Junio C Hamano
2009-03-30 10:11 ` [PATCHv2 4/4] Rename push.default to push.mode Santi Béjar
2009-03-30 10:42 ` Michael J Gruber
2009-03-30 12:37 ` Santi Béjar [this message]
2009-03-30 13:06 ` Michael J Gruber
2009-03-30 13:45 ` Jeff King
2009-03-30 14:47 ` Michael J Gruber
2009-03-30 18:02 ` Jeff King
2009-03-31 12:55 ` Michael J Gruber
2009-03-31 13:08 ` Jeff King
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=adf1fd3d0903300537i41d4aef3g49ab6bde9343cbc5@mail.gmail.com \
--to=santi@agolina.net \
--cc=git@drmicha.warpmail.net \
--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).