All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Groeger <GROEGES@uk.ibm.com>
To: git@vger.kernel.org
Subject: Use of new .gitattributes working-tree-encoding attribute across different platform types
Date: Wed, 27 Jun 2018 07:54:52 +0000	[thread overview]
Message-ID: <OF5D40FE06.C18CD7CD-ON002582B9.002B7A02-002582B9.002B7A07@notes.na.collabserv.com> (raw)
In-Reply-To: 

Hi, 

Sorry for incomplete post earlier. Here is the full post:


In the latest version of git a new attribute has been added, working-tree-encoding. The release notes states: 

'The new "working-tree-encoding" attribute can ask Git to convert the
   contents to the specified encoding when checking out to the working
   tree (and the other way around when checking in).'
 We have been using this attribute on our z/OS systems using a version of git from Rocket software to convert files to EBCDIC for quite a while now. On other platforms (Linux, AIX etc) git ignored this attribute and therefore left the files in ASCII.

We have common code that is supposed to be usable across different platforms and hence different file encodings. With the full support of the working-tree-encoding in the latest version of git on all platforms, how do we have files converted to different encodings on different platforms?
I could not find anything that would allow us to say 'if platform = z/OS then encoding=EBCDIC else encoding=ASCII'.   Is there a way this can be done?
 
 
  
 
Thanks
 Steve Groeger
 Java Runtimes Development
 IBM Hursley
 IBM United Kingdom Ltd
 Tel: (44) 1962 816911 Mobex: 279990 Mobile: 07718 517 129
 Fax (44) 1962 816800
 Lotus Notes: Steve Groeger/UK/IBM
 Internet: groeges@uk.ibm.com  
   
 
Unless stated otherwise above:
 IBM United Kingdom Limited - Registered in England and Wales with number 741598.
 Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU      
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


             reply	other threads:[~2018-06-27  7:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27  7:54 Steve Groeger [this message]
2018-06-27 17:38 ` Use of new .gitattributes working-tree-encoding attribute across different platform types Torsten Bögershausen
2018-06-28  2:44 ` brian m. carlson
2018-06-28 14:34   ` Jeff King
2018-06-28 17:21     ` Lars Schneider
2018-06-28 17:27       ` Jeff King
2018-07-01 17:56         ` brian m. carlson
2018-07-02 18:17           ` Jeff King
2018-07-03 16:01             ` Junio C Hamano
2018-07-02 12:13     ` Steve Groeger
2018-07-02 14:09       ` Lars Schneider
2018-07-02 18:20         ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27  7:50 Steve Groeger

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=OF5D40FE06.C18CD7CD-ON002582B9.002B7A02-002582B9.002B7A07@notes.na.collabserv.com \
    --to=groeges@uk.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.