From: Luke Diamand <luke@diamand.org>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: git-p4: nicodeDecodeError in ./t9822-git-p4-path-encoding.sh
Date: Mon, 21 Sep 2015 08:52:33 +0100 [thread overview]
Message-ID: <55FFB741.4080304@diamand.org> (raw)
In-Reply-To: <55FFAB62.8050106@diamand.org>
On 21/09/15 08:01, Luke Diamand wrote:
> Lars,
>
> When I run t9822-git-p4-path-encoding.sh, the last test fails (it's
> supposed to pass) with the following backtrace.
>
> This is with 'next' at 3dd15c02a81a280c83c8d5e32c6cb71a64177ca6.
>
> Any ideas as to what I'm doing wrong?
>
I think this is probably user error!
Luke
next prev parent reply other threads:[~2015-09-21 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 7:01 git-p4: nicodeDecodeError in ./t9822-git-p4-path-encoding.sh Luke Diamand
2015-09-21 7:52 ` Luke Diamand [this message]
2015-09-21 8:22 ` Lars Schneider
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=55FFB741.4080304@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.