git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git repo vs project level authorization

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 5, 2016, 21:59 UTC
Message-ID
<xmqqvauy2g19.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAAqgmoO+7cLZHpX61=Mh7PjqrCUc0qyFD=C+sjVat_+KPhisbw@mail.gmail.com>
ken edward <kedward777@gmail.com> writes:
Show 6 quoted lines
> I am currently using svn with apache+mod_dav_svn to have a single
> repository with multiple projects. Each of the projects is controlled
> by an access control file that lists the project path and the allowed
> usernames.
>
> Does git have this also? where is the doc?

It is customary not to mix unrelated projects into a single repository in the Git land. Some hosting solutions give access control per branches, and some others give access control per repositories.

Previous: Sitaram Chamarty
Message 4 of 4 in “git repo vs project level authorization”
  1. ken edwardDec 5, 2016
  2. Fredrik GustafssonDec 5, 2016
  3. Sitaram ChamartyDec 7, 2016
  4. Junio C HamanoDec 5, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.