From: "Constantine Plotnikov" <constantine.plotnikov@gmail.com>
To: git@vger.kernel.org
Subject: Bug: UTF-16, UCS-4 and non-existing encodings for git log result in incorrect behavior
Date: Wed, 12 Nov 2008 16:32:23 +0300 [thread overview]
Message-ID: <85647ef50811120532h778769ddx69f0b111dbad359a@mail.gmail.com> (raw)
If UTF-16[BE|LE] or UCS-4[BE|LE] encodings are used with git log, the
git completes successfully but commit messages and author information
are not shown. I suggest that git should fail with fatal error if such
zero producing encoding is used.
If the incorrect encoding name is used, the git log does not perform
any re-encoding, but just display commits in their native encoding. I
suggest that git should fail with fatal error in this case as well.
Regards,
Constantine
next reply other threads:[~2008-11-12 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 13:32 Constantine Plotnikov [this message]
2008-11-12 14:22 ` Bug: UTF-16, UCS-4 and non-existing encodings for git log result in incorrect behavior Johannes Schindelin
[not found] ` <85647ef50811120727j730cb6e3lf4103c200d042fb9@mail.gmail.com>
2008-11-12 16:15 ` Johannes Schindelin
2008-11-12 16:17 ` Alexander Gavrilov
2008-11-12 16:42 ` Johannes Schindelin
2008-11-12 16:58 ` Alexander Gavrilov
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=85647ef50811120532h778769ddx69f0b111dbad359a@mail.gmail.com \
--to=constantine.plotnikov@gmail.com \
--cc=git@vger.kernel.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).