Re: [RFC/WIP 0/2] Documentation clean-up: git commands
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 23, 2009, 16:22 UTC
- Message-ID
- <7vwsag5hva.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <1237818533-31577-1-git-send-email-git@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
> - Do we want it this way (`git command`)?
That's my personal preference but other people may differ; wasn't there an issue with "man" backend losing the typesetting information?
> - How to prepare: 1 patch per file/per 5 files/per 50 changes? > - How to submit: single patch once ready or whole series at end (5 years > from now)? > - How to send: Bother the list or send pull requests only?
How about a fork of git.git on repo.or.cz that branches from 1.6.2 and that:
- does not pull from git.git/master unless absoletely necessary; and - contains only these clean-up changes and nothing else?
A bonus point would be for a publically reachable pages rendered out of the tip of this "documentation updates" repository, so that people can view it, compare it with www.kernel.org/pub/software/git/docs/.
I would love to have a separate "documentation maintainer" in the longer run, and it would be great if your tree becomes it. I can start pulling from you, forwarding any documentation patches your way.
Thanks.