From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>, git@vger.kernel.org
Subject: Re: Git *accepts* a branch name, it can't identity in the future?
Date: Sun, 20 Aug 2017 14:41:11 +0530 [thread overview]
Message-ID: <1503220271.5824.9.camel@gmail.com> (raw)
In-Reply-To: <829ac9ed-857d-84bf-2374-6a36b1d0aff1@kdbg.org>
On Sun, 2017-08-20 at 10:20 +0200, Johannes Sixt wrote:
> It is not Git's fault that your terminal converts an invalid UTF-8
> sequence (that your script produces) to �. Nor is it when you paste that
> character onto the command line, that it is passed as a (correct) UTF-8
> character.
>
You're right. I just now realise how I missed the line between "what's
seen by us" and "what's seen by the program".
> Perhaps this helps (untested):
>
> $ git branch -m done/$(printf '\x93')doc-fix done/dic-fix
>
This one helped, thanks.
--
Kaartic
next prev parent reply other threads:[~2017-08-20 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 7:51 Git *accepts* a branch name, it can't identity in the future? Kaartic Sivaraam
2017-08-20 8:20 ` Johannes Sixt
2017-08-20 9:11 ` Kaartic Sivaraam [this message]
2017-08-20 8:33 ` Jeff King
2017-08-20 10:00 ` Kaartic Sivaraam
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=1503220271.5824.9.camel@gmail.com \
--to=kaarticsivaraam91196@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.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.
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 NNTP newsgroup(s).