git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Wincent Colaiuta <win@wincent.com>
Date
Nov 7, 2007, 08:03 UTC
Message-ID
<D739E20F-BCEF-418C-AE6F-A74C4ACEA4FA@wincent.com>
In-Reply-To
<47310ACF.4030103@gmail.com>
El 7/11/2007, a las 1:46, Francesco Pretto escribió:
Show 36 quoted lines
> Junio C Hamano ha scritto:
>>
>> Honestly speaking, I am not too thrilled about making the
>> cvs-migration document much longer than what it currently is.
>>
>
> Honestly speaking, you've spent too much time in looking for every  
> possible
> objections against these simple additions. At least it should be  
> less than the
> time I've spent in measuring every single word of this patch, hoping  
> you could
> consider them for inclusion. You gave me lot of attentions (I am  
> grateful of this,
> really) so I should probably be surprised of the cleanliness of git  
> code, of the
> rigor of the code style, of the clarity of the documentation. But  
> unfortunately,
> I am not. I simply tried to make this document more useful and  
> helpful for a
> wider audience of people that could ever consider of using git in  
> their life.
> And yes, I decided to so because I had trouble myself during initial  
> configurations.
> What's the problem if a document called "git for CVS users" is more  
> explicated?
> What's the problem if it contains as many as possible informations  
> to set up
> git in a viable way and, hopefully, to learn something on how it  
> does work?
>
> I'm sad. Not only because you refused a documentation patch, but  
> because i could
> have sent a "Bug: Documentation Sucks!" to the ml and i would have  
> obtained the
> same thing: nothing.

On the contrary, I think you received some excellent, high-quality feedback. The process that you've been participating in over the last few days is exactly why the Git codebase is as good as it is; only the very best patches get accepted, and those which aren't "the very best" receive detailed feedback that help the submitter to turn weak patches into strong ones. The process works very well and the proof is in the pudding (the quality of the product).

Cheers, Wincent

Previous: J. Bruce FieldsNext: Steffen Prohaska
Message 16 of 18 in “Documentation: enhanced "git for CVS users" doc about shared repositories”
  1. Documentation: enhanced "git for CVS users" doc about shared repositoriesFrancesco Pretto, Nov 5, 2007
  2. Junio C HamanoNov 5, 2007
  3. Francesco PrettoNov 6, 2007
  4. Johannes SchindelinNov 6, 2007
  5. Francesco PrettoNov 6, 2007
  6. Francesco PrettoNov 6, 2007
  7. Junio C HamanoNov 6, 2007
  8. Francesco PrettoNov 7, 2007
  9. Johannes SchindelinNov 7, 2007
  10. Francesco PrettoNov 7, 2007
  11. AghilesNov 7, 2007
  12. Steffen ProhaskaNov 7, 2007
  13. Andreas EricssonNov 7, 2007
  14. David KastrupNov 7, 2007
  15. J. Bruce FieldsNov 7, 2007
  16. Wincent ColaiutaNov 7, 2007
  17. Steffen ProhaskaNov 7, 2007
  18. J. Bruce FieldsNov 7, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.