kfogel@collab.net writes:
> Seriously: you have as much "right" to commit as any committer. And
> you are as responsible for what you commit as any committer. So when
> you're unsure of a specific change, you should ask first, and when
> you're pretty confident, you can go ahead and commit it -- this is how
> everyone else operates too. And if there's ever a vote among the full
> committers (rare, but who knows), then your vote counts the same as
> anyone else's.
I guess I should add: you are running 'make check' first, right? Or
to be more complete:
'make check'
'make svncheck'
'make davcheck'
Basically, if a commit breaks the build or the test suite, that's more
embarrassing than if it introduces a subtle bug that no one expected
:-). So for code changes, there are at least these sanity checks to
give you some confidence.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 2 03:13:54 2003