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 (Oct 2017, #06; Fri, 27)
Date: Sun, 29 Oct 2017 14:13:59 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1710291409390.6482@virtualbox> (raw)
In-Reply-To: <xmqq7evhc7nw.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Fri, 27 Oct 2017, Junio C Hamano wrote:
> * cc/git-packet-pm (2017-10-22) 6 commits
> - Git/Packet.pm: extract parts of t0021/rot13-filter.pl for reuse
> - t0021/rot13-filter: add capability functions
> - t0021/rot13-filter: add packet_initialize()
> - t0021/rot13-filter: improve error message
> - t0021/rot13-filter: improve 'if .. elsif .. else' style
> - t0021/rot13-filter: refactor packet reading functions
>
> Parts of a test to drive the long-running content filter interface
> has been split into its own module, hopefully to eventually become
> reusable.
>
> Expecting a reroll.
> The original unfortunately is quite broken in error detection
> cases to make the result sub-par as a standalone module before it
> gets fixed.
Would you terribly mind adding a SQUASH??? with my suggested fix for
PERL_NO_MAKEMAKER?
Otherwise, the Windows build will keep failing for `pu`.
> * jr/ssh-wrappers (2017-10-24) 5 commits
> - ssh: 'simple' variant does not support --port
> - ssh: 'simple' variant does not support -4/-6
> - ssh: 'auto' variant to select between 'ssh' and 'simple'
> - connect: split ssh command line options into separate function
> - connect: split git:// setup into a separate function
> (this branch uses bw/protocol-v1.)
Likewise, this needs a SQUASH??? to remove the uplink$X before
(over-)writing uplink, to pass the test suite on Windows.
Of course, if we could eventually have Continuous Testing of individual
*branches* (instead of `pu`), then we would not have to see those test
failures in every effing single build of `pu`. I mean, there is no need to
test things after they were tested already, and failed, right?
Ciao,
Dscho
next prev parent reply other threads:[~2017-10-29 13:14 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 [this message]
2017-10-29 14:18 ` Junio C Hamano
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=alpine.DEB.2.21.1.1710291409390.6482@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.
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).