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

Re: [PATCH] Simplified GIT usage guide

From
Willy Tarreau <w@1wt.eu>
Date
Dec 19, 2008, 06:33 UTC
Message-ID
<20081219063301.GA6800@1wt.eu>
In-Reply-To
<bd6139dc0812121716w73ea1145w7f870e887e00adc0@mail.gmail.com>
On Sat, Dec 13, 2008 at 02:16:34AM +0100, Sverre Rabbelier wrote:
Show 9 quoted lines
> On Sat, Dec 13, 2008 at 02:04, David Howells <dhowells@redhat.com> wrote:
> >  (3) You put some non-basic stuff in the basic section (branching - this isn't
> >     ordinarily useful, IMHO), but you miss other stuff out ('git rm' for
> >     example).
> 
> Erm, branching is not ordinarily useful? I think you're Doing It Wrong
> (TM) then, since branching is a Big Thing (also TM) in DVC, not using
> branches would be a bit like only using the first 4 gears in a car;
> sure, it's possible, but you're missing all that extra power!

People who want to use it as a CVS replacement don't realize that they're using branches. They work in their local "master" branch, and don't realize that when they fetch updates, they fetch them into a different branch.

CVS people are afraid of branches, so trying to explain them how they can do what they're used to is better than telling them they'll have to do what they're afraid of.

I found David's howto quite understandable. I've taught Git to people who only knew about SVN and to people who had never heard about any SCM at all. I tried to use the same approach each time, and while I noticed that explaining how Git works and why it works like that appeared obvious to the newbies, it was very awkward with SVN users. I switched to something more like David's approach for those people and it helped a lot. They have plenty of time after that to discover the tool by themselves.

I really think that David should maintain his doc after applying a few fixes to it, just like Jeff maintains his own. Also, having several docs out of the tree is better for a user looking for different analysis of the tool than having everything offered as the product's documentation, provided the links are easy to find (might be linked to from the Git doc).

Willy
Previous: Sverre RabbelierNext: Nicolas Pitre
Message 22 of 38 in “Simplified GIT usage guide”
  1. Simplified GIT usage guideDavid Howells, Dec 12, 2008
  2. Miklos VajnaDec 12, 2008
  3. David HowellsDec 12, 2008
  4. Miklos VajnaDec 12, 2008
  5. David HowellsDec 13, 2008
  6. Miklos VajnaDec 13, 2008
  7. Johannes SchindelinDec 12, 2008
  8. David HowellsDec 12, 2008
  9. Sverre RabbelierDec 12, 2008
  10. Aidan Van DykDec 12, 2008
  11. Nick AndrewDec 13, 2008
  12. Ping YinDec 14, 2008
  13. Paul E. McKenneyDec 19, 2008
  14. Junio C HamanoDec 19, 2008
  15. Paul E. McKenneyDec 19, 2008
  16. valdis.kletnieks@vt.eduDec 24, 2008
  17. Johannes SchindelinDec 19, 2008
  18. Paul E. McKenneyDec 19, 2008
  19. Jakub NarebskiDec 12, 2008
  20. David HowellsDec 13, 2008
  21. Sverre RabbelierDec 13, 2008
  22. Willy TarreauDec 19, 2008
  23. Nicolas PitreDec 13, 2008
  24. J. Bruce FieldsDec 12, 2008
  25. J. Bruce FieldsDec 13, 2008
  26. David HowellsDec 13, 2008
  27. Jeff GarzikDec 12, 2008
  28. Chris FriesenDec 12, 2008
  29. David HowellsDec 13, 2008
  30. Junio C HamanoDec 13, 2008
  31. Nick AndrewDec 13, 2008
  32. Nicolas PitreDec 12, 2008
  33. Junio C HamanoDec 13, 2008
  34. Matthieu MoyDec 14, 2008
  35. Marcin SlusarzDec 14, 2008
  36. C. Scott AnanianDec 19, 2008
  37. Michael J GruberDec 19, 2008
  38. C. Scott AnanianDec 19, 2008

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.