On 5/06/2021 1:06 am, Paul Gilmartin wrote:
On Fri, 4 Jun 2021 13:21:06 +0800, David Crayford wrote:
You can do this but you're going to have to jump through some hoops.
First you need to upload the repo from a zip file or whatever. Then you
will have to tag all the files ISO8859-1 using the "chtag -R -tc
ISO8859-1 ." command and hope there are no binary files.
Why not the increasingly popular UTF-8?
Git on z/OS used to only support IBM-1047 and ISO8859-1. The latest
release supports many more code pages including UTF-8 but the default
when cloning a repo
from external hosting such Github is to tag ISO8859-1. Whatever flicks
yer switch.
ISPF Edit/View supports UTF-8
tagged files splendidly, within the limitations of the terminal emulator.
(Does NFS tagging support UTF-8 (IBM CCSID 1208)?)
We dual-mounted some NFS: one binary mountpoint, one translated.
Since I've started working for Rocket I'm an enhanced ASCII convert. I
treat the file system as an ASCII environment and tag everything
ISO8859-1. Although I might give UTF-8 a whirl now that you mention it.
We don't use NFS. I use Linux (Ubuntu running on WSL) with a locally
mounted sshfs file system that uses sftp to sync with z/OS. Works well.
Microsoft have done a great job with Windows interoperability with Linux.
Then you need to convert the repo to a bare repositeory.
|git clone --mirror path_to_source_repository path_to_bare_repository |
...
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
