git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Santos <hello@brighterdan.com>
Cc: git@vger.kernel.org
Subject: Re: Git show only showing ASCII chars problem
Date: Fri, 23 Jul 2021 12:37:00 -0700	[thread overview]
Message-ID: <xmqqfsw4n7oj.fsf@gitster.g> (raw)
In-Reply-To: <924b70af-1e55-0944-0f45-ab28cff1e98d@brighterdan.com> (Daniel Santos's message of "Fri, 23 Jul 2021 18:20:34 +0100")

Daniel Santos <hello@brighterdan.com> writes:

> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
> git show

Thanks for a report, but sorry, it is *not* "steps to reproduce your
issue", as people who do not have the commit you have trouble with
checked out would not see your issue reproduced by typing "git
show".  Something like this:

    $ mkdir newdir; cd newdir; git init
    $ echo 'ç ã õ' >file; git add file
    $ git commit -m "add file with non-ascii contents"
    $ git show

may be detailed enough for people to try reproducing what I see
(i.e. creation of a single-line file is shown with its non-ascii
contents).

By the way, if the problem is that your pathnames in the patch are
protected from corruption by quoting, perhaps

    $ git config --global core.quotepath false

may be what you are looking for.  I couldn't tell from your report
if that is the case, though.

Thanks.


      parent reply	other threads:[~2021-07-23 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 17:20 Git show only showing ASCII chars problem Daniel Santos
2021-07-23 18:06 ` Felipe Contreras
2021-07-23 19:37 ` Junio C Hamano [this message]

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=xmqqfsw4n7oj.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=hello@brighterdan.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 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).