git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Bharat Suvarna'" <bharat.bs84@icloud.com>, <git@vger.kernel.org>
Subject: RE: Git with Lader logic
Date: Wed, 18 Mar 2015 15:53:25 -0400	[thread overview]
Message-ID: <00bd01d061b5$331874c0$99495e40$@nexbridge.com> (raw)
In-Reply-To: <5F9B9EBF-CD4D-42A8-8A0C-9806702231A1@icloud.com>

On March 17, 2015 7:34 PM, Bharat Suvarna wrote:
> 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.

Many PLC programs either store their project code in XML, L5K or L5X (for
example), TXT, CSV, or some other text format or can import and export to
text forms. If you have a directory structure that represents your project,
and the file formats have reasonable line separators so that diffs can be
done easily, git very likely would work out for you. You do not have to have
the local .git repository in the same directory as your working area if your
tool has issues with that or .gitignore. You may want to use a GUI client to
manage your local repository and handle the commit/push/pull/merge/rebase
functions as I expect whatever PLC system you are using does not have git
built-in.

To store binary PLC data natively, which some tools use, I expect that those
who are better at git-conjuring than I, could provide guidance on how to
automate binary diffs for your tool's particular file format.

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

  parent reply	other threads:[~2015-03-18 19:53 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
2015-03-18 19:53 ` Randall S. Becker [this message]
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='00bd01d061b5$331874c0$99495e40$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --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).