Right now with
svn:ignore properties under SVN all works as a charm, but it becomes problematic to figure out what exactly is ignored if there is a need.
Consider following workflow:
- developer downloads a ZIP with official release content
- imports it into his repository (SVN or GIT)
- performs installation
- makes changed to a code
- tries to commit
At commit time all stuff, that In-Portal have created during runtime in /system/ folder is displayed as changes that needs to be commited. This is very problematic for a newcomer to determine what really needs to be commited and what not.
To solve this I'm proposing to add
.gitignore files where
.cvsignore files used to be. This not only eases In-Portal transition to GIT (if that happens), but also allows to reset
svn:ignore properties with a single
bash command by scanning created
Here are current values:
All of above properties were retrieved using following command executed on "in-portal" module checkout directory:
As you can see from a table there 3 folder types where this property is set:
- /system folder and it's sub-folders
- some strange folder
- tools/home folder
I've highlighted properties, that are no longer needed (in my opinion) in bold.