Pushing after merge considered harmful

[Gordon Tyler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/26/2010 10:08 AM, Matthew D. Fuller wrote:
> Asking after it the other way around basically boils down to "explain
> what $X is doing without having to understand what $X does".  Trying
> to do that means ANYTHING ends up being a bunch of independent special
> cases, which is impossible to learn, and impossible to extrapolate
> from.  It's an annoyance I fight against continually professionally,
> and it's one of my pet peeves in bzr support.
> 
> Trying to pass information along as that bunch of special cases is
> doomed to failure, and it can't help BUT frustrate people, who'll take
> it as meaning the tool itself is a pile of cobbled-up special cases,
> when it's nothing of the sort.  While there ARE unfortunately some
> ugly special cases in bzr (the bound/checkout thing being high on the
> list), MOST of the behavior is Obvious(tm) from the interaction of the
> rather few underlying pieces.

Thank you for putting into words what I've often felt when trying to
communicate to the QA department at work. :)

Ciao,
Gordon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLXwfNAAoJEIrPJfWinA2uy38H/iilx3BaY3y/Z4GXocsf3+CM
La7okZhlERg9+azYDjIgwGR2e46tAbJKsI66rHEfREm9KUm8xqCIZ4T+M990CBDG
44fo1wUBoB3vyA7zTveyFyJxoaa2t2Xo/u19DVdyOLWTdMmve8LEX7CQnOl/fwhS
ZskBq8pM7VU870xztVw6wo3jJsuRChePlBcbTj+bSddbve+0/SknaLh9C2txbzVF
6aRXHd7VlzTb58V565riZAQQGLSJbTeypGhIe9z8uJ6DtJbJFk9f/UL2NX1jOCmN
0t/+s+bK+yw2Vs+AAuANPv9FFHtHdu8bFdtqklZiWmTGRWEveWkbEUQO9HMtWAk=
=AI4K
-----END PGP SIGNATURE-----