From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2016, #06; Tue, 19)
Date: Wed, 20 Jul 2016 10:20:33 +0200 [thread overview]
Message-ID: <CBEE46F3-5497-43D6-BA5A-217C7AD55B48@gmail.com> (raw)
In-Reply-To: <xmqqk2ghdysg.fsf@gitster.mtv.corp.google.com>
On 20 Jul 2016, at 00:54, Junio C Hamano <gitster@pobox.com> wrote:
>
> [New Topics]
>
> ...
>
> * jk/push-scrub-url (2016-07-14) 1 commit
> (merged to 'next' on 2016-07-19 at 6ada3f1)
> + push: anonymize URL in status output
>
> "git fetch http://user:pass@host/repo..." scrubbed the userinfo
> part, but "git push" didn't.
>
> Will merge to 'master'.
t5541-http-push-smart.sh "push status output scrubs password" fails on
next using Travis CI OS X:
https://travis-ci.org/git/git/jobs/145960712
https://api.travis-ci.org/jobs/145960712/log.txt?deansi=true (non JS)
I think the test either fails because of OS X or because of the
used Apache version (Travis CI Linux uses 2.2.22 and OS X uses 2.2.26).
I haven't done any further investigation.
According to my Travis CI Git bisect script the failure starts to appear
with the commit that introduced the test in 882d49c
"push: anonymize URL in status output":
https://travis-ci.org/larsxschneider/git/jobs/146027836
- Lars
next prev parent reply other threads:[~2016-07-20 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 22:54 What's cooking in git.git (Jul 2016, #06; Tue, 19) Junio C Hamano
2016-07-20 8:20 ` Lars Schneider [this message]
2016-07-20 11:32 ` [PATCH] t5541: fix url scrubbing test when GPG is not set Jeff King
2016-07-21 6:44 ` Lars Schneider
2016-07-20 15:58 ` What's cooking in git.git (Jul 2016, #06; Tue, 19) Pranit Bauva
2016-07-22 15:52 ` 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=CBEE46F3-5497-43D6-BA5A-217C7AD55B48@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).