-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/24/2010 11:03 AM, John J. McDonough wrote:
On Wed, 2010-11-24 at 10:22 -0500, Eric "Sparks"
Christensen wrote:
> 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?
--McD
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJM7UhQAAoJEDbiLlqcYamx8dkQAKaV9rXL9EEdDpmO2bxWR0QH
jGRg9TGCpui/BFbRou2GhRQnbttACbHUiwd8ZsE5tLPm3BJxUWkAo9yWMX87xwBa
Rq9AuMh2l+DOUi9X9dSJ7AkPdGy6L7w+G/dN+ZmLiu1VWaydU3Pkxp83mjwvx7t5
C2Te7g/q88sx+JMJGJFjUeTMaHZjcUK0j4/vqf7r+jNjnu0mefR7p+3wiLAqffJL
Wo6KBZc13dmgJxNRI0x/wyClXg7BuKya6SZBziZcvmu1PGwy+4GJ8UwFCFv3hJ2l
tGjTTf5ehl3NqpSy5XsPJpmkZagkTSnrBJHi80/TKnt4UhU4hOritu7PuV6ljBJt
sV3BQpJeGTFfqaUtee1KP8Q/65n5Z4BR9DkZWw/fRILnWQKDb9T5y9bWscu0+72w
vSrx3+QguUJ8r6o1uViROxR9jqcxEG5HMi0xH0HfOAJl0nELMrhnswlPDpsgzV+F
oV1t16nYpOmi8EARBKtLywhvxzIt7NE3QQPxXdIA7K6boMj3CmnUzfUW3OrWepjV
IpkNm8anCjPP1yidDTYDWo9Bqvx9iI84TR85VAhT5IuLbL8Tg/cnKP67XuHpKdbt
mQ62Bkjs3Clig/j52IBBDHfPn4Ls1Z+/82CXHr4HwY9PbuhyJgRLuOQ3bl88sPyz
v4vx/Fbh/uFv3OXqEF/+
=7TlU
-----END PGP SIGNATURE-----