[clug] Using GIT as a 'records system'

Ben Nizette bn at niasdigital.com
Wed Dec 22 16:47:50 MST 2010

On 23/12/2010, at 8:47 AM, steve jenkin wrote:

> 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']

I don't think there's any access control more fine-grained than individual repos, mainly as git doesn't really have much in the way of a concept of files (well no more than is required to make the 'porcelain' layer user-friendly).

I've done this kind of thing in the past using 'git submodule', using that you can leave access controls at a per-repo level but tie the repos together in to what ever logical kind of hierarchy you need.


> 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
> -- 
> linux mailing list
> linux at lists.samba.org
> https://lists.samba.org/mailman/listinfo/linux

More information about the linux mailing list