You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Git is better than Subversion in that it can do “self-ignoring ignores”, that is, temporary ignores. For example, creating a git-repo/committed-xml-dir/.gitignore:
/.gitignore
/*.xml
This will cause all XML files in that directory to then be ignored, and if you do a git status the .gitignore won't show up either. This allows files to be temporarily ignored locally without having to commit anything. In contrast, Subversion ignores are handled via a the svn:ignore property, and you can't do svn propset svn:ignore "*.xml" ." and then ignore the ignore viasvn:ignore "." .`—it doesn't work.
The text was updated successfully, but these errors were encountered:
I would say git is better just because of the whole svn:ignore thing in general. I can't see what is ignored without using svn itself. If I want to ignore something, but I don't want to force everyone else to ignore it, I have to change my svn:ignore settings and then every time I commit, I need to exclude that particular property. It's just so much more of pain vs. cat .gitignore
Git is better than Subversion in that it can do “self-ignoring ignores”, that is, temporary ignores. For example, creating a
git-repo/committed-xml-dir/.gitignore
:This will cause all XML files in that directory to then be ignored, and if you do a
git status
the.gitignore
won't show up either. This allows files to be temporarily ignored locally without having to commit anything. In contrast, Subversion ignores are handled via a thesvn:ignore
property, and you can't dosvn propset svn:ignore "*.xml" ." and then ignore the ignore via
svn:ignore "." .`—it doesn't work.The text was updated successfully, but these errors were encountered: