Molle Bestefich wrote:
> I was trying to say that a QA tool in form of a SVN pre-commit hook
> seems like a perfect fit. The entire infrastructure to run an
> external application to check a commit before carrying it out,
> approve the commit, send appropriate error messages back to the SCM
> clie
> If you want central control of what's happening in the repository,
> Subversion seems like the way to go.
Better to fix the design of the repository, so that it can't be
broken in the first place, than to try putting band-aids in place
to cover the gaps.
Wow, way out of scope.
Sure, a Portage
Dan Armak wrote:
On Saturday 29 April 2006 15:21, Fernando J. Pereda wrote:
The commit marked with @ is a special comit called a 'merge'.
I hope that clarifies the merge tracking part.
You just described what merging is. Svn can do that too with svn merge. But,
if I merge changesets from branch
