From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] Support git:// with old MinGW
Date: Mon, 29 Apr 2019 15:04:35 -0700 (PDT) [thread overview]
Message-ID: <pull.137.git.gitgitgadget@gmail.com> (raw)
The MinGW project (which can now be considered "old", as mingw-w64 is the
standard thing to use nowadays, since it also supports 64-bit builds) had
some problems with our sideband feature, and in Git for Windows <2.x, we
introduced a config setting to still allow using the git:// protocol by
forcing off the sideband channel.
Let's contribute this patch to upstream Git, at long last.
Thomas Braun (1):
mingw: optionally disable side-band-64k for transport
Documentation/config.txt | 2 ++
Documentation/config/sendpack.txt | 5 +++++
send-pack.c | 14 +++++++++++++-
3 files changed, 20 insertions(+), 1 deletion(-)
create mode 100644 Documentation/config/sendpack.txt
base-commit: 8104ec994ea3849a968b4667d072fedd1e688642
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-137%2Fdscho%2Fsideband-bug-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-137/dscho/sideband-bug-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/137
--
gitgitgadget
next reply other threads:[~2019-04-29 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 22:04 Johannes Schindelin via GitGitGadget [this message]
2019-04-29 22:04 ` [PATCH 1/1] mingw: optionally disable side-band-64k for transport Thomas Braun via GitGitGadget
2019-04-29 22:10 ` Eric Sunshine
2019-04-29 23:17 ` Johannes Schindelin
2019-04-30 6:21 ` Johannes Sixt
2019-04-30 22:33 ` Johannes Schindelin
2019-04-30 22:55 ` Johannes Sixt
2019-05-03 8:42 ` Johannes Schindelin
2019-04-29 23:19 ` brian m. carlson
2019-04-30 22:37 ` Johannes Schindelin
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=pull.137.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--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).