From: "Frans Klaver" <fransklaver@gmail.com>
To: git@vger.kernel.org
Subject: Re: Does git have "Path-Based Authorization"?
Date: Sun, 02 Oct 2011 08:43:02 +0200 [thread overview]
Message-ID: <op.v2pox0g70aolir@keputer> (raw)
In-Reply-To: <CAN0CFw3ZDcXtD7WChjkT1Vg0cU_u==4KCHo8ff-ccbyxZ8xWjg@mail.gmail.com>
On Sun, 02 Oct 2011 05:34:43 +0200, Grant <emailgrant@gmail.com> wrote:
> That's true. I hope to be able to give different developers access to
> different parts of the code. I really don't know if this will work.
> I just don't want my code to be stolen and I'm trying to find some way
> to prevent that from happening.
To me it seems like you don't trust your developers? If you run a
business and you hire external developers, have them sign an NDA.
Should be legally binding.
I as a developer would be severely insulted if my boss tried to keep
me away from some code, just because he was afraid it might get stolen.
If you don't trust them, fix your trust and relationship, not some tool.
Just my two cents.
Have a good one,
Frans
next prev parent reply other threads:[~2011-10-02 6:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 23:43 Does git have "Path-Based Authorization"? Grant
2011-10-01 0:05 ` Carlos Martín Nieto
2011-10-01 1:31 ` Grant
2011-10-01 1:34 ` Nguyen Thai Ngoc Duy
2011-10-01 1:43 ` Grant
2011-10-01 2:09 ` david
2011-10-01 13:06 ` Jakub Narebski
2011-10-02 0:00 ` Grant
2011-10-02 1:27 ` Sitaram Chamarty
2011-10-02 2:53 ` Grant
2011-10-02 3:24 ` Nguyen Thai Ngoc Duy
2011-10-02 3:34 ` Grant
2011-10-02 6:38 ` Andreas Krey
2011-10-02 6:43 ` Frans Klaver [this message]
2011-10-02 14:50 ` Enrico Weigelt
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=op.v2pox0g70aolir@keputer \
--to=fransklaver@gmail.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).