Re: [PATCH] Documentation: enhanced "git for CVS users" doc about shared repositories

From: Steffen Prohaska <prohaska@zib.de>
Date: Nov 7, 2007, 07:35 UTC
Message-ID: <DED2A61B-B5AE-4BAA-942A-18A61924611E@zib.de>
In-Reply-To: <3abd05a90711061736r4c969cddj348c006615ffbdd6@mail.gmail.com>

On Nov 7, 2007, at 2:36 AM, Aghiles wrote:

Show 19 quoted lines

> Hello,
>>
>> Remember, those who read "git for CVS users" are _unwilling_ to  
>> spend the
>> time reading git documentation (at least for the most part).  If they
>> encounter something which is not useful to them, they will not  
>> just ignore
>> it, they will stop reading.
>>
>
> I must disagree with this analysis (although I didn't read the  
> content of the
> patch you are commenting). People that are not really interested in  
> git will
> find many reasons to stop reading the manual anyway. Those who really
> want to migrate (such as we did) are looking for every tiny bit of  
> information.
> (We googled git commands and error messages because we didn't
> find what we needed in the docs)

Could you be a bit more specific? What are the most important points that you did not found in the documentation?

It would be interesting if you could share some details. Sending patches that would fix the deficiencies would even be superior ;)

> The docs are not perfect and somewhat unequal in content but I prefer
> more information than less, at this particular stage of git  
> development.

I agree if it is git specific information. But, personally, I'd get a bit annoyed if a git specific document tried to teach me how to manage Unix accounts. BTW, useradd and such would not help me at all, because I need to talk to my admin anyway and he adds an account to the LDAP database.

	Steffen