4 ms·

I think the issues are: 1) "a global ignore file" 2) In subversion you have to run a 44 character long command with one subcommand, two flags, and two file a

I think the issues are: 1) "a global ignore file" 2) In subversion you have to run a 44 character long command with one subcommand, two flags, and two file arguments. In git you have to do.... nothing.

parfe 15y ago
So edit ~/.subversion/config and never deal with ignores again. Acting like subversion does this in a less than optimal way is ignoring what the command is actually doing. With subversion method you can check out a subtree. Git can do no such thing. I prefer git, but being able to check out say, only /project/doc/ or /project/static/images/, is useful in subversion.
- burgerbrain 15y ago
  I'm saying that for myself, for my needs, subversion's way is less optimal. No acting required. I don't need to only check out certain trees in my.. [checks] 20MB repo. What I do need is a way to ignore a rotating handful of files.
reemrevnivek 15y ago
1) Git ignore is not a global (to the repository) file, either. Both SVN and Git have per-user (not per-repository) settings, and they have very similar functions. .gitignore is only global by common practice, according to http://www.kernel.org/pub/software/scm/git/docs/gitignore.html#_description http://www.kernel.org/pub/software/scm/git/docs/gitignore.ht... you can use: ...a .gitignore file in the same directory as the path, or in any parent directory, with patterns in the higher level files (up to the toplevel of the work tree) being overridden by those in lower level files down to the directory containing the file. A global .gitignore feature in the toplevel of the work tree is just one way of using the .gitignore feature. 2) If character count is important, svn ps -R -F i . is only 16 characters long, and does the same thing (if you name your file 'i', since we're golfing here). I readily admit that this is INFINITELY longer than the Git version.

parfe 15y ago

So edit ~/.subversion/config and never deal with ignores again. Acting like subversion does this in a less than optimal way is ignoring what the command is actually doing. With subversion method you can check out a subtree. Git can do no such thing. I prefer git, but being able to check out say, only /project/doc/ or /project/static/images/, is useful in subversion.

burgerbrain 15y ago
I'm saying that for myself, for my needs, subversion's way is less optimal. No acting required. I don't need to only check out certain trees in my.. [checks] 20MB repo. What I do need is a way to ignore a rotating handful of files.

reemrevnivek 15y ago

1) Git ignore is not a global (to the repository) file, either. Both SVN and Git have per-user (not per-repository) settings, and they have very similar functions. .gitignore is only global by common practice, according to http://www.kernel.org/pub/software/scm/git/docs/gitignore.html#_description http://www.kernel.org/pub/software/scm/git/docs/gitignore.ht... you can use: ...a .gitignore file in the same directory as the path, or in any parent directory, with patterns in the higher level files (up to the toplevel of the work tree) being overridden by those in lower level files down to the directory containing the file. A global .gitignore feature in the toplevel of the work tree is just one way of using the .gitignore feature. 2) If character count is important, svn ps -R -F i . is only 16 characters long, and does the same thing (if you name your file 'i', since we're golfing here). I readily admit that this is INFINITELY longer than the Git version.