From: Kevin D <me@ikke.info>
To: Bharat Suvarna <bharat.bs84@icloud.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git with Lader logic
Date: Wed, 18 Mar 2015 12:29:36 +0100 [thread overview]
Message-ID: <20150318112936.GC11832@vps892.directvps.nl> (raw)
In-Reply-To: <5F9B9EBF-CD4D-42A8-8A0C-9806702231A1@icloud.com>
On Tue, Mar 17, 2015 at 11:33:54PM +0000, Bharat Suvarna wrote:
> Hi
>
> I am trying to find a way of using version control on PLC programmers like Allen Bradley PLC. I can't find a way of this.
>
> Could you please give me an idea if it will work with Plc programs. Which are basically Ladder logic.
>
I'm not familiar with these programs, so I can't give you specific
advice about this.
Although git is not very picky about the contents, it is optimized to
track text files. Things like showing diffs and merging files only works
on text files.
Git can track binary files, but there are some disadvantages:
- Diff / merge doesn't work well
- Compression is often difficult, so the repository size may grow
depending on the size of the things stored
These disadvantages are not limited to only git, other SCM systems also
have to deal with these problems.
So if the Ladder logic is represented as text source, there is no
problem with it. If it'sbinary, there might be other sollutions better
suited.
Kevin
next prev parent reply other threads:[~2015-03-18 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 23:33 Git with Lader logic Bharat Suvarna
2015-03-18 11:29 ` Kevin D [this message]
2015-03-18 19:53 ` Randall S. Becker
2015-03-18 22:28 ` Doug Kelly
2015-03-18 22:38 ` Randall S. Becker
2015-03-19 7:14 ` Bharat Suvarna
2015-03-19 21:17 ` Kevin D
2015-03-27 15:09 ` Martin Pettersson
2015-03-27 15:39 ` Junio C Hamano
2015-03-27 16:32 ` Martin Pettersson
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=20150318112936.GC11832@vps892.directvps.nl \
--to=me@ikke.info \
--cc=bharat.bs84@icloud.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).