Wolfram Posted May 4, 2017 Report Share Posted May 4, 2017 Hiho. Most of our team is working on Windows, but we also have a few Mac users. Now every(?) time somebody commits something on a Mac, there will usually be several files that are unmodified, but are commited/need to be committed anyway, as they are marked as "Only filesystem permissions changed". In the diff window the info given is "Filesystem permissions changed from NOT_DEFINED to [...]". As we really don't care about these (our main platform is Windows, and all our projects use Unity), we'd like to be able to prevent these changes from being committed/recognized, as they create a lot of clutter, making the Plastic client harder to use for our Designers and so on. We didn't find a setting to influence this behaviour - is there another workaround (or CLI trick?) to have the Mac client and/or the whole database ignore all filesystem permissions? Thanks a lot! :o) Link to comment Share on other sites More sharing options...
psantosl Posted May 4, 2017 Report Share Posted May 4, 2017 You can stop using Macs... :-P No, seriously, we don't have such a setting at this point... So, yes, each time a file is touched on Mac, the permission will be set. But, after that, it shouldn't be modified anymore... unless explicitly changed on Mac. Makes sense? Link to comment Share on other sites More sharing options...
Wolfram Posted May 8, 2017 Author Report Share Posted May 8, 2017 On 5/4/2017 at 9:38 PM, psantosl said: You can stop using Macs... :-P Tell that to our designers x-D OK, thanks for the quick answer! Guess we'll just have to live with it then for now. Link to comment Share on other sites More sharing options...
ioioio Posted August 22, 2021 Report Share Posted August 22, 2021 I am experiencing this problem, too. Filesystem permissions changed from NOT_DEFINED to dr-xr-xr-x Most of our team is on Windows, and I am on Mac. How do I avoid flooding my changesets with irrelevant files changing permissions? Link to comment Share on other sites More sharing options...
calbzam Posted August 23, 2021 Report Share Posted August 23, 2021 Hi, I'm afraid this previous comment still applied to this topic: Quote No, seriously, we don't have such a setting at this point... So, yes, each time a file is touched on Mac, the permission will be set. But, after that, it shouldn't be modified anymore... unless explicitly changed on Mac. Makes sense? Regards, Carlos. Link to comment Share on other sites More sharing options...
ioioio Posted August 25, 2021 Report Share Posted August 25, 2021 On 8/23/2021 at 5:03 AM, calbzam said: Carlos, where is this information stored? I don't mind running a simple command line script to undo all files in the changeset for which only permissions have changed. Link to comment Share on other sites More sharing options...
calbzam Posted August 26, 2021 Report Share Posted August 26, 2021 Hi, Each time a file is touched on Mac, the permission will be set. If I properly understand, the problem is some files are commited with not extra changes but just the permission changes? Regards, Carlos. Link to comment Share on other sites More sharing options...
Wolfram Posted August 30, 2021 Author Report Share Posted August 30, 2021 On 8/26/2021 at 10:19 AM, calbzam said: If I properly understand, the problem is some files are commited with not extra changes but just the permission changes? Yes, exactly. Link to comment Share on other sites More sharing options...
calbzam Posted September 14, 2021 Report Share Posted September 14, 2021 Hi, The permissions changes are stored in the database in addition to the rest of the file changes. Each time a file is touched on Mac, the permission will be set. But, after that, it shouldn't be modified anymore... unless explicitly changed again on Mac, right? Regards, Carlos. Link to comment Share on other sites More sharing options...
Wolfram Posted September 14, 2021 Author Report Share Posted September 14, 2021 Well, we often get changesets for already existing assets which are by themselves NOT modified in that changeset, but the FS permission changes from "NOT_DEFINED" to [...] are still being committed. It is not a bug or causes any problems - but it kindof "spams" the changesets with useless (for us) information, which makes it hard to compare changes. A solution could be to have a repository-wide setting whether to ignore or to use file system permissions. Link to comment Share on other sites More sharing options...
calbzam Posted September 15, 2021 Report Share Posted September 15, 2021 I'm afraid we don't have such a feature at the moment. There is a feature in the Plastic GUI --> Preferences --> OtherOptions --> Check content when the file timestamp is modifyed to set it as "Changed". I think it could help to avoid checkin files that don't have actual changes in the file content. Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now