[clug] Using GIT as a 'records system'

[steve jenkin]

haven't FGFI this yet, thought the group might give me some clues...
[because I've never used GIT or read the manuals in detail. have a hazy
overview only.]

Can GIT allow fine-grained access control to specific trees/sets of files?

It can obviously store files and add/delete/change 'pages',
but another essential element of 'Record Management Systems' is access
control...

The ordinary worker can't be allowed to see the confidential CEO
correspondence... (Mergers, downsizing, ...)

Could this be handled by multiple tree-heads?
[In SVN they might be called 'tags']

Thanks In Advance.

steve j

-- 
Steve Jenkin, Info Tech, Systems and Design Specialist.
0412 786 915 (+61 412 786 915)
PO Box 48, Kippax ACT 2615, AUSTRALIA

sjenkin at canb.auug.org.au http://members.tip.net.au/~sjenkin