2011-01-26, 12:06
Hi,
I've got a Web app on a server, that may dynamically create some directories in "/public/sites/medias" from the inside of the app.
I've got no problem so far to tell Git to ignore everything _actually_ in "public/sites/medias", but the problem is when users begin to create new dirs and add files like these :
/public/sites/medias
---------------------/images
---------------------------/4
-----------------------------/my_pic.jpg
I can't understand why the hell does Git always want to track them and then say "/public/sites/medias/images/4/my_pic.jpg needs update" when I pull a new version of the app.
Here is my actual .gitignore :
public/sites/
config/**
!config/routes.rb
db/*.sql*
log/*.log
tmp/*
*.swp
How can I tell Git to _never_ever_ look inside "/public/sites" no more and totally forget about what could ever happen inside this directory ?
Any help highly appreciated, thanks
I've got a Web app on a server, that may dynamically create some directories in "/public/sites/medias" from the inside of the app.
I've got no problem so far to tell Git to ignore everything _actually_ in "public/sites/medias", but the problem is when users begin to create new dirs and add files like these :
/public/sites/medias
---------------------/images
---------------------------/4
-----------------------------/my_pic.jpg
I can't understand why the hell does Git always want to track them and then say "/public/sites/medias/images/4/my_pic.jpg needs update" when I pull a new version of the app.
Here is my actual .gitignore :
public/sites/
config/**
!config/routes.rb
db/*.sql*
log/*.log
tmp/*
*.swp
How can I tell Git to _never_ever_ look inside "/public/sites" no more and totally forget about what could ever happen inside this directory ?
Any help highly appreciated, thanks