From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: local shared directory
Date: Thu, 17 Mar 2016 19:32:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20160317T202654-413@post.gmane.org> (raw)
In-Reply-To: 20160317181115.4e806350@digimed.co.uk
Neil Bothwick <neil <at> digimed.co.uk> writes:
>
> On Thu, 17 Mar 2016 18:19:21 +0100, hw wrote:
>
> > how can I make it so that multiple users on a system who create
> > files in a local, shared directory do have write access to files
> > created by other users within the shared directory?
>
> ACLs.
Hmmmmm. Perhaps one of our most knowledgable folks would like to
share how to setup git locally on this machine and use it's features
to 'skin the cat' vis a vis this problem. The more I learn about git
the more I realize it is boundless on creative usages, so I'd be
very surprise, if one of our smarter members does not know how to
do this with git.
The git advantage would be that if the work ever needs to span countries or
continents, it should be then be trivial to migrate the repo(s) to the
cloud, github or similar distributed/container environments.
curiously,
James
next prev parent reply other threads:[~2016-03-17 19:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 17:19 [gentoo-user] local shared directory hw
2016-03-17 18:11 ` Neil Bothwick
2016-03-17 19:32 ` James [this message]
2016-03-17 20:59 ` Alan McKinnon
2016-03-17 22:38 ` Rich Freeman
2016-03-17 23:10 ` Michael Orlitzky
2016-03-17 23:34 ` Neil Bothwick
2016-04-23 12:15 ` hw
2016-04-23 12:42 ` hw
2016-04-23 14:42 ` how to share a directory tree with files in it with multiple users (Re: [gentoo-user] local shared directory) hw
2016-04-23 15:12 ` Michael Orlitzky
2016-05-07 15:12 ` hw
2016-05-07 23:24 ` Alan McKinnon
2016-05-14 16:26 ` solved: " hw
2016-04-23 14:56 ` [gentoo-user] local shared directory Neil Bothwick
2016-05-14 16:23 ` hw
2016-05-14 22:43 ` Neil Bothwick
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=loom.20160317T202654-413@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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