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

Re: Git in a Nutshell guide

From
JJJonas Juselius <jonas.juselius@chem.uit.no>
Date
Nov 20, 2007, 11:34 UTC
Message-ID
<1195558478.10369.8.camel@localhost>
In-Reply-To
<3057F6F3-BEAA-447A-AB79-A0AFB7DB8826@lrde.epita.fr>
On Mon, 2007-11-19 at 17:49 +0100, Benoit Sigoure wrote:
> You can create a repository on repo.or.cz then :)
I will :=)
Show 6 quoted lines
> 
> As it is often the case different people happen to work on similar  
> things without knowing each other.  I started http://repo.or.cz/w/ 
> tutorial.git which is meant to be a big Beamer presentation that  
> presents Git thoroughly.  I wrote some ideas but didn't start to  
> write the slides.  Just in case you want to have a look.

Thanks, there are certainly some things in that document that I ought to consider incorporating in the guide. But for now I'll let it rest for a little while, because I don't have time to mess with it. Patches are always welcome ;)

Show 9 quoted lines
> One of the things you said in your guide is that Git is easy to  
> learn.  I think this is wrong.  Git is way more complicated than most  
> other SCMs, especially compared to SVN.  Its documentation is far  
> behind, compared to what other SCMs have.  There is no real user  
> guide and the man pages are incomplete, at best.  I know saying this  
> is a bit harsh, especially to the people out there that are working  
> and sending patches to improve the documentation, but I think we have  
> to admit that it's true, even though Git is making progress on this  
> aspect.

Well, you are right to some extent. But it's this gap I would like to fill with the nutshell guide. The "for normal people" slogan is meant to refer to non-technical developers (like scientists). I should probably include a little section in the intro describing distributed vs. centralised SCMs in general.

Thanks for the input,
.jonas.
Previous: Daniel BarkalowNext: Jakub Narebski
Message 13 of 40 in “Git in a Nutshell guide”
  1. Jonas JuseliusNov 19, 2007
  2. Jakub NarebskiNov 19, 2007
  3. Jonas JuseliusNov 19, 2007
  4. David KågedalNov 22, 2007
  5. Jakub NarebskiNov 23, 2007
  6. Brian DowningNov 19, 2007
  7. Brian DowningNov 19, 2007
  8. Nicolas PitreNov 19, 2007
  9. Jakub NarebskiNov 19, 2007
  10. Jonas JuseliusNov 19, 2007
  11. Benoit SigoureNov 19, 2007
  12. Daniel BarkalowNov 19, 2007
  13. Jonas JuseliusNov 20, 2007
  14. Jakub NarebskiNov 20, 2007
  15. Jan HudecNov 21, 2007
  16. Jakub NarebskiNov 21, 2007
  17. jhud7196@artax.karlin.mff.cuni.czNov 22, 2007
  18. Jonas JuseliusNov 22, 2007
  19. Jonathan del StrotherNov 22, 2007
  20. Johannes SchindelinNov 22, 2007
  21. jhud7196@artax.karlin.mff.cuni.czNov 22, 2007
  22. Lars HjemliNov 19, 2007
  23. Jonas JuseliusNov 19, 2007
  24. Benoit SigoureNov 19, 2007
  25. Lars HjemliNov 19, 2007
  26. Benoit SigoureNov 19, 2007
  27. J. Bruce FieldsNov 19, 2007
  28. Matthieu MoyNov 19, 2007
  29. Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys.Matthieu Moy, Nov 19, 2007
  30. Junio C HamanoNov 19, 2007
  31. Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys.Matthieu Moy, Nov 19, 2007
  32. Matthieu MoyNov 19, 2007
  33. Benoit SigoureNov 19, 2007
  34. Matthieu MoyNov 19, 2007
  35. Benoit SigoureNov 19, 2007
  36. J. Bruce FieldsNov 19, 2007
  37. Junio C HamanoNov 19, 2007
  38. Matthieu MoyNov 19, 2007
  39. Junio C HamanoNov 19, 2007
  40. Matthieu MoyNov 19, 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.