Jump to content

Ignore changes in Filesystem Permissions?


Wolfram

Recommended Posts

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

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

  • 4 years later...

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

  • 2 weeks later...

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

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

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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...