From: ZheNing Hu <adlternative@gmail.com>
To: "Git List" <git@vger.kernel.org>,
"Derrick Stolee" <stolee@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Question: What's the best way to implement directory permission control in git?
Date: Wed, 27 Jul 2022 16:56:12 +0800 [thread overview]
Message-ID: <CAOLTT8QusNzdO1mHqQFPz84pznYSpFWJunroRGXQ7qk6sJjeYg@mail.gmail.com> (raw)
if there is a monorepo such as
git@github.com:derrickstolee/sparse-checkout-example.git
There are many files and directories:
client/
android/
electron/
iOS/
service/
common/
identity/
list/
photos/
web/
browser/
editor/
friends/
boostrap.sh
LICENSE.md
README.md
Now we can use partial-clone + sparse-checkout to reduce
the network overhead, and reduce disk storage space size, that's good.
But I also need a ACL to control what directory or file people can fetch/push.
e.g. I don't want a client fetch the code in "service" or "web".
Now if the user client use "git log -p" or "git sparse-checkout add service"...
or other git command, git which will download them by
"git fetch --filter=blob:none --stdin <oid>" automatically.
This means that the git client and server interact with git objects
(and don't care about path) we cannot simply ban someone download
a "path" on the server side.
What should I do? You may recommend me to use submodule,
but due to its complexity, I don't really want to use it :-(
ZheNing Hu
next reply other threads:[~2022-07-27 8:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 8:56 ZheNing Hu [this message]
2022-07-27 9:17 ` Question: What's the best way to implement directory permission control in git? Ævar Arnfjörð Bjarmason
2022-07-28 14:54 ` ZheNing Hu
2022-07-28 15:50 ` Ævar Arnfjörð Bjarmason
2022-07-29 1:48 ` Elijah Newren
2022-07-29 14:22 ` ZheNing Hu
2022-07-29 14:57 ` rsbecker
2022-07-29 13:15 ` ZheNing Hu
2022-07-27 9:24 ` Thomas Guyot
2022-07-29 12:49 ` ZheNing Hu
2022-07-29 23:50 ` Emily Shaffer
2022-07-31 16:15 ` ZheNing Hu
2022-08-01 10:14 ` Han-Wen Nienhuys
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=CAOLTT8QusNzdO1mHqQFPz84pznYSpFWJunroRGXQ7qk6sJjeYg@mail.gmail.com \
--to=adlternative@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=stolee@gmail.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).