From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2016, #01; Tue, 3)
Date: Wed, 4 May 2016 08:09:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1605040808340.9313@virtualbox> (raw)
In-Reply-To: <xmqqshxykb9k.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Tue, 3 May 2016, Junio C Hamano wrote:
> * js/http-custom-headers (2016-04-27) 1 commit
> (merged to 'next' on 2016-04-27 at 0c97a50)
> + http: support sending custom HTTP headers
>
> HTTP transport clients learned to throw extra HTTP headers at the
> server, specified via http.extraHeader configuration variable.
>
> Will merge to 'master'.
This misses the rather crucial support for `git -c ... submodule ...` that
I sent out earlier. I will send out another iteration with the indentation
as per your wishes. Please let me know whether you want the second patch
as a separate "patch series" instead.
Ciao,
Dscho
next prev parent reply other threads:[~2016-05-04 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 22:49 What's cooking in git.git (May 2016, #01; Tue, 3) Junio C Hamano
2016-05-04 6:09 ` Johannes Schindelin [this message]
2016-05-04 10:04 ` Ævar Arnfjörð Bjarmason
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=alpine.DEB.2.20.1605040808340.9313@virtualbox \
--to=johannes.schindelin@gmx.de \
--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.
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).