git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: saurabh@stockal.com, git@vger.kernel.org
Subject: Re: Whether Git supports directory level access or not?
Date: Tue, 7 Jul 2015 09:16:34 +0200	[thread overview]
Message-ID: <559B7CD2.1040507@web.de> (raw)
In-Reply-To: <705bdbdc6a8195d59203bcb1f3027714@stockal.com>

On 07.07.15 08:40, saurabh@stockal.com wrote:
> Hi,
> 
> Please let me know whether Git supports directory level access or not.
> 
> For example :- Consider the structure with one repository consisting of sub directories for each product.
> main_repo:
>    dir1 dir
>    dir2 dir
>    shared-dir dir
>    private dir
> One group(user) of developers has access to dir1 and shared-dir while the other group(user) has access to dir2 and shared-resources.
> Just for context, both dir1 and dir2 require shared-dir to be checked out for building the products.
> 
> And private dir is only accessible by admin(repo owner).
> 
> Regards
> Saurabh gaur

Git is a distributed VCS.
If you do a clone, all information is available on your local machine.

Solution:
Use a different repo for private stuff, in your example you need 4 repos,
which has the advantage that each product has it's own repo.

HTH

  reply	other threads:[~2015-07-07  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  6:40 Whether Git supports directory level access or not? saurabh
2015-07-07  7:16 ` Torsten Bögershausen [this message]
2015-07-07  7:20 ` Jacob Keller
2015-07-07 17:03   ` Junio C Hamano
2015-07-07 23:03     ` Jacob Keller

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=559B7CD2.1040507@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=saurabh@stockal.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).