Bug 127745 - Changing directory permissions will have an option to apply recursive permissions of files within the directory
Summary: Changing directory permissions will have an option to apply recursive permiss...
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus   
(Show other bugs)
Version: 4
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-13 10:22 UTC by Joel Bryan T. Juliano
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-09-04 14:23:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Joel Bryan T. Juliano 2004-07-13 10:22:10 UTC
Description of problem: No options to change certain directory
permissions with recursivity in File Properties window.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Matthew Miller 2005-04-26 15:44:03 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 2 Marius Andreiana 2005-08-19 19:20:48 UTC
I agree this option would be useful. Still not present in FC4. 
Made tests, by default the permissions are applied only to selected folders,
excluding subfolders (which is correct).

Changing status to ASSIGNED.

Comment 3 Alexander Larsson 2006-09-04 14:23:53 UTC
Availible in rawhide.


Note You need to log in before you can comment on or make changes to this bug.