-----BEGIN PGP SIGNED MESSAGE-----
On 11/24/2010 11:03 AM, John J. McDonough wrote:
On Wed, 2010-11-24 at 10:22 -0500, Eric "Sparks"
> But once the change is in the repo it is too late. You shouldn't commit
> a change before it is QA'd. If the change is in the repo then there is
> a high chance that the change will make it to the final guide without
> being checked.
No, no, no. The whole point of a repo like git is to make working
collaboratively easy. For that to work you need to commit frequently.
The idea that somehow what is in the repo is sacred is a view that makes
working together hard. Sure, it may have held some sway back in the RCS
days before collaborative RCSs were available, or maybe even with CVS
where doing anything is so bloody hard and fraught with risk, but wit
git there is no argument not to commit, certainly not if you have a way
to identify QAed commits.
Can you mark pages as draft or just entire documents?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----