From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: <hackerp@suddenlink.net>
Cc: git@vger.kernel.org
Subject: Re: GIT for Microsoft Access projects
Date: Mon, 8 Jun 2015 19:14:58 +0300 [thread overview]
Message-ID: <20150608191458.9f6a93b0259a8ca0324c8dc0@domain007.com> (raw)
In-Reply-To: <20150608094517.GY06Y.31914.root@txifep02>
On Mon, 8 Jun 2015 9:45:17 -0500
<hackerp@suddenlink.net> wrote:
[...]
> My question is, will GIT work with MS access forms, queries, tables,
> modules, etc?
[...]
Git works with files. So in principle it will work with *files*
containing your MS access stuff.
But Git will consider and treat those files as opaque blobs of data.
That is, you will get no "fancy diffing" like asking Git to graphically
(or otherwise) show you what exact changes have been made to a
particular form or query between versions X and Y of a given MS access
document -- all it will be able to show you is commit messages
describing those changes.
So... If you're fine with this setting, Git will work for you,
but if not, it won't.
One last note: are you really sure you want an SCM/VCS tool to manage
your files and not a document management system (DMS) instead?
I mean stuff like Alfresco (free software by the way) and the like.
next prev parent reply other threads:[~2015-06-08 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 14:45 GIT for Microsoft Access projects hackerp
2015-06-08 16:14 ` Konstantin Khomoutov [this message]
2015-06-08 22:02 ` Randall S. Becker
2015-06-09 13:54 ` Sitaram Chamarty
2015-06-09 17:19 ` git lock files (Was: GIT for Microsoft Access projects) Stefan Beller
2015-06-09 18:21 ` hackerp
2015-06-09 18:50 ` Konstantin Khomoutov
2015-06-09 19:08 ` Stefan Beller
2015-06-10 7:47 ` Fredrik Gustafsson
2015-06-10 15:22 ` Stefan Beller
2015-06-10 16:32 ` git lock files Junio C Hamano
2015-06-15 8:52 ` Thomas Koch
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=20150608191458.9f6a93b0259a8ca0324c8dc0@domain007.com \
--to=kostix+git@007spb.ru \
--cc=git@vger.kernel.org \
--cc=hackerp@suddenlink.net \
/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).