Timeline for How to Git-Ignore Symlinks on a Magento Module installed by composer
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 4, 2013 at 17:41 | history | edited | Alex | CC BY-SA 3.0 |
Fix for the case that we have a file "foo" and then also a file "foo.css"
|
Jul 1, 2013 at 17:23 | review | Suggested edits | |||
Jul 1, 2013 at 19:01 | |||||
Jun 13, 2013 at 18:05 | history | edited | Vinai | CC BY-SA 3.0 |
Remove the leading ./ from the symlinks that find finds.
|
Jun 13, 2013 at 18:04 | comment | added | Vinai |
Simple solution: find * ... . Will update my answer.
|
|
Jun 13, 2013 at 17:53 | comment | added | Vinai | Actually, that breaks the grep... well, maybe there is a good way to clean the path up anyway... | |
Jun 13, 2013 at 17:52 | history | edited | Vinai | CC BY-SA 3.0 |
Revert previous change since it introduces breakage
|
Jun 13, 2013 at 17:35 | history | edited | Vinai | CC BY-SA 3.0 |
Remove leading ./ of the resulting records
|
Jun 13, 2013 at 17:32 | comment | added | Vinai |
Works fine for me with the leading . , yes. Else sed to the rescue: find . -type l -not -exec grep -q "{}" .gitignore \; -print | sed 's/^\.\///'
|
|
Jun 13, 2013 at 17:03 | comment | added | Alex |
this generates path's like ./foo/bar .. I think we have to remove the first . - did it work for you like that?
|
|
Jun 12, 2013 at 12:00 | vote | accept | Alex | ||
Jun 11, 2013 at 15:44 | history | answered | Vinai | CC BY-SA 3.0 |