threads / discuss / 41320

SV: Using Git for Cobol source

Subject: SV: Using Git for Cobol source

## tl;dr

2 messages between Feb 3, 2016 and Feb 3, 2016.

replies: 1people: 2as markdown or json

johnsen· Feb 3, 2016, 09:19 UTC · lore
Hi
I wonder if it is ok to use Git for source control for Cobol programs and take advantage of parallel development ?
Today we are using VSS and needs to be replaced. Our Cobol development is done by an Eclipse tool (Micro Focus Enterprise Developer)

Regards _______________________________________________

Per Jørgen Johnsen | Technical Coordinator
DNB Bank ASA
Norway
________________________________
 This email with attachments may be confidential and intended solely for the use of the individual or entity to whom it is addressed. The email may contain legally protected information. If you have received this communication in error, be aware that making use of the information, forwarding it, copying it, or disclosing its content to other persons, is strictly prohibited and may be punishable by law. Please inform the sender about the error in transmission immediately.
________________________________
Randall S. Becker· Feb 3, 2016, 13:30 UTC · re: johnsen · lore

RE: Using Git for Cobol source

On February 3, 2016 4:20 AM, Per Jørgen Johnsen wrote:
> Subject: SV: Using Git for Cobol source
> I wonder if it is ok to use Git for source control for Cobol programs and
take
> advantage of parallel development ?
> 
> Today we are using VSS and needs to be replaced. Our Cobol development is
> done by an Eclipse tool (Micro Focus Enterprise Developer)

COBOL should be no problem for git. The one caution I would have for you is that if you happen to be using fixed-format mode with column-based sequence numbers (that would be really old COBOL 74 mode), the sequence numbers may give false positives on diff results. If you have those, lose them. This would apply to VSS also, so you're probably not using those anyway.

If you are functional in VSS for COBOL, you should be fine. Your challenge will be migrating history, which is possible, but will involve some effort.

Regards, Randall

-- Brief whoami: NonStop&UNIX developer since approximately UNIX(421664400)/NonStop(211288444200000000) -- In my real life, I talk too much.

← back to recent threads