SvnBridge Frustrations
This is how I am feeling at the moment (more below):
One of the major disadvantages of having to dog food the source control I am using to write the source control is that it is incredibly fragile.
It is fairly easy to violate some invariant in a non obvious way, which make for problems down the road. The problem is that those problems are symptoms, not the real issue. As a result, I have this:
I try to clean it up often, but at one point I got to SvnBridge5.
Thank god that SVN has such a good patching mechanism.
Comments
that picture cracks me up. i know exactly how you feel.
Does this mean that with SVN Bridge will have the ability for someone to create patch, and for a reviewer to apply and commit patch? This is the one thing I would like to see in TFS but we don't have. That way when new people come onto a project, you can watch what they are doing for awhile to be sure they are implementing the level of quality you expect on the project.
Fervent,
Yes, it does have this ability. This is actually client side stuff only, btw.
Exactly. ;D
But client side with Team Explorer (TFS) you cannot get this ability.
I was thinking that logically you should get this behavior with SVNBridge as it should appear and act like SVN on the client side.
Comment preview