From: Jeff King <peff@peff.net>
To: Scott McKellar <mck9@swbell.net>
Cc: "git@vger.kernel.org " <git@vger.kernel.org>
Subject: Re: Support for EBCDIC
Date: Thu, 3 Jul 2014 13:34:13 -0400 [thread overview]
Message-ID: <20140703173413.GC20571@sigill.intra.peff.net> (raw)
In-Reply-To: <1404355152.86116.YahooMailNeo@web184805.mail.gq1.yahoo.com>
On Wed, Jul 02, 2014 at 07:39:12PM -0700, Scott McKellar wrote:
> Is Git supposed to be usable in an environment where the execution character set is EBCDIC?
Not really.
In addition to the cases you found (and I would be surprised if there
are not more, such as our reimplementation of ctype.h), we assume:
- we can intermingle ASCII from string literals with user data to form
diffs, commit objects, network protocols, etc. This is actually a
problem not just for EBCDIC, but for any encoding which is not an
ASCII-superset (like UTF-16).
- many outputs from git should be ASCII in order to interoperate with
the outside world (object headers, network protocols, etc).
So I'd be surprised if things worked well in an EBCDIC environment (but
I have never worked with one, so maybe I do not understand all of the
implications).
-Peff
next prev parent reply other threads:[~2014-07-03 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 2:39 Support for EBCDIC Scott McKellar
2014-07-03 17:34 ` Jeff King [this message]
2014-07-03 20:01 ` Jason Pyeron
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=20140703173413.GC20571@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=mck9@swbell.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.
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).