While using Nitpick I think it is committing the entire project from the root and not just limiting itself to the Nitpick database as it used to. This is using the svn VCS backend.
Here's the situation. In subversion 1.6 if you were inside the .nitpick directory and the svn:external was in the project root (to avoid infinitely recursive externals) then the Foreign projects would still be marked as such.
However, with subversion 1.7 this is no longer the case. Inside .nitpick 'svn stat' now shows a status of ? for the external instead of X.
While using Nitpick I think it is committing the entire project from the root and not just limiting itself to the Nitpick database as it used to. This is using the svn VCS backend.
Date: 2013-08-14 02:47:19
User: travisb
This doesn't happen with just a plain Nitpick database, but does happen if you have an SVN foreign repository pointing to the same branch.
Date: 2013-08-14 02:54:51
User: travisb
Here's the situation. In subversion 1.6 if you were inside the .nitpick directory and the svn:external was in the project root (to avoid infinitely recursive externals) then the Foreign projects would still be marked as such. However, with subversion 1.7 this is no longer the case. Inside .nitpick 'svn stat' now shows a status of ? for the external instead of X.
Date: 2013-09-06 15:09:09
User: travisb
This is still broken in my meta repository.
Date: 2013-09-06 15:22:48
User: travisb
Looks to be because of a stray newline creating an empty foreign project.
Tracked by Nitpick