From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2017, #06; Fri, 27)
Date: Sun, 29 Oct 2017 23:18:35 +0900 [thread overview]
Message-ID: <xmqq7eve9gw4.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1710291409390.6482@virtualbox> (Johannes Schindelin's message of "Sun, 29 Oct 2017 14:13:59 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Would you terribly mind adding a SQUASH??? with my suggested fix for
> PERL_NO_MAKEMAKER?
> ..
> Likewise, this needs a SQUASH??? to remove the uplink$X before
> (over-)writing uplink, to pass the test suite on Windows.
Surely I don't mind; please just send me something I can "git am"
(or something I can "git apply --index && git commit -m SQAUSH???"
would be sufficient) for these; letting me construct and/or type a
patch from pieces of discussion messages is a sure way to introduce
further issues for Windows, as I don't have a way to test any such
change before I push them out.
Thanks.
next prev parent reply other threads:[~2017-10-29 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 8:32 What's cooking in git.git (Oct 2017, #06; Fri, 27) Junio C Hamano
2017-10-27 18:50 ` Stefan Beller
2017-11-07 2:00 ` sb/submodule-recursive-checkout-detach-head Junio C Hamano
2017-11-07 17:05 ` sb/submodule-recursive-checkout-detach-head Stefan Beller
2017-11-08 0:21 ` sb/submodule-recursive-checkout-detach-head Junio C Hamano
2017-10-28 17:13 ` What's cooking in git.git (Oct 2017, #06; Fri, 27) Kaartic Sivaraam
2017-10-29 13:13 ` Johannes Schindelin
2017-10-29 14:18 ` Junio C Hamano [this message]
2017-10-29 15:18 ` Johannes Schindelin
2017-10-30 1:27 ` 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=xmqq7eve9gw4.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).