Directory and files permission on repo file listing #104

Closed
opened 2025-11-02 03:09:00 -06:00 by GiteaMirror · 17 comments
Owner

Originally created by @joubertredrat on GitHub (Dec 1, 2016).

Hi guys,

One big git feature is versioning file and directory permissions (chmod) and I think that is good ideia to display this as optional on repository listing, as example below.

What you think guys?

chmod_wireframe

Originally created by @joubertredrat on GitHub (Dec 1, 2016). Hi guys, One big git feature is versioning file and directory permissions (chmod) and I think that is good ideia to display this as optional on repository listing, as example below. What you think guys? ![chmod_wireframe](https://cloud.githubusercontent.com/assets/1520407/20794301/bffeac24-b7b2-11e6-98aa-db81765cd089.png)
GiteaMirror added the type/featureissue/stalereviewed/wontfix labels 2025-11-02 03:09:00 -06:00
Author
Owner

@lunny commented on GitHub (Dec 1, 2016):

Windows?

@lunny commented on GitHub (Dec 1, 2016): Windows?
Author
Owner

@joubertredrat commented on GitHub (Dec 1, 2016):

Windows?

Sorry for windows users, but this power is privilege only for elite, linux users 🐧

But @lunny I liked your question, I will test to see if you have git server on windows, if it can versioning chmod from linux, I think that yes because git is OS agnostic.

@joubertredrat commented on GitHub (Dec 1, 2016): > Windows? Sorry for windows users, but this power is privilege only for elite, linux users :star: :penguin: But @lunny I liked your question, I will test to see if you have git server on windows, if it can versioning chmod from linux, I think that yes because git is OS agnostic.
Author
Owner

@bkcsoft commented on GitHub (Dec 2, 2016):

@lunny Git stores file-permissions as metadata (just that Windows throws them away on checkout), so there's no compat issue here :)

@joubertredrat as always, "benchmark" new features that hits Git, cache if appropriate :)

@bkcsoft commented on GitHub (Dec 2, 2016): @lunny Git stores file-permissions as metadata (just that Windows throws them away on checkout), so there's no compat issue here :) @joubertredrat as always, "benchmark" new features that hits Git, cache if appropriate :)
Author
Owner

@lunny commented on GitHub (Dec 2, 2016):

@bkcsoft you are right. Forgot that.

@lunny commented on GitHub (Dec 2, 2016): @bkcsoft you are right. Forgot that.
Author
Owner

@tboerger commented on GitHub (Dec 2, 2016):

But Git doesn't keep all flags.

@tboerger commented on GitHub (Dec 2, 2016): But Git doesn't keep all flags.
Author
Owner

@joubertredrat commented on GitHub (Dec 2, 2016):

Ok guys, I'm noob but I will try to implement this.

@joubertredrat commented on GitHub (Dec 2, 2016): Ok guys, I'm noob but I will try to implement this.
Author
Owner

@thibaultmeyer commented on GitHub (Dec 2, 2016):

@joubertredrat I think is better to make it optional (create a configuration key on app.ini).

take care about the overhead too

@thibaultmeyer commented on GitHub (Dec 2, 2016): @joubertredrat I think is better to make it optional (create a configuration key on app.ini). take care about the overhead too
Author
Owner

@joubertredrat commented on GitHub (Dec 2, 2016):

@0xbaadf00d yes, on first post I saw this

I think that is good ideia to display this as optional on repository listing

Other good option is set to chmod be numeric 755 or string representation -rw-rw-r--.

@joubertredrat commented on GitHub (Dec 2, 2016): @0xbaadf00d yes, on first post I saw this > I think that is good ideia to display this as optional on repository listing Other good option is set to chmod be numeric `755` or string representation `-rw-rw-r--`.
Author
Owner

@bkcsoft commented on GitHub (Dec 2, 2016):

@tboerger it keeps 777 which are the ones that are relevant (from the screenshot)

@bkcsoft commented on GitHub (Dec 2, 2016): @tboerger it keeps `777` which are the ones that are relevant (from the screenshot)
Author
Owner

@stale[bot] commented on GitHub (Feb 17, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 17, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@joubertredrat commented on GitHub (Feb 27, 2019):

Oh, I need to try to implement this now that I know to programming in golang

@joubertredrat commented on GitHub (Feb 27, 2019): Oh, I need to try to implement this now that I know to programming in golang
Author
Owner

@lunny commented on GitHub (Feb 28, 2019):

@joubertredrat but I think make it configurable is better.

@lunny commented on GitHub (Feb 28, 2019): @joubertredrat but I think make it configurable is better.
Author
Owner

@joubertredrat commented on GitHub (Feb 28, 2019):

Hi @lunny

This is the idea. For me, this can be enabled or not by configuration and in configuration define if you want to see numeric 755 or string representation -rw-rw-r--. What you think?

@joubertredrat commented on GitHub (Feb 28, 2019): Hi @lunny This is the idea. For me, this can be enabled or not by configuration and in configuration define if you want to see numeric `755` or string representation `-rw-rw-r--`. What you think?
Author
Owner

@lunny commented on GitHub (Feb 28, 2019):

@joubertredrat and maybe not display that to keep compatible with before?

@lunny commented on GitHub (Feb 28, 2019): @joubertredrat and maybe not display that to keep compatible with before?
Author
Owner

@joubertredrat commented on GitHub (Feb 28, 2019):

@lunny Yes, if not defined on configuration, don't display by default

@joubertredrat commented on GitHub (Feb 28, 2019): @lunny Yes, if not defined on configuration, don't display by default
Author
Owner

@stale[bot] commented on GitHub (Apr 29, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 29, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (May 13, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (May 13, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#104