{"thread":{"id":"13603","subject":"git tutorial","startedAt":"2008-05-21T16:42:33Z","lastAt":"2008-05-22T09:35:49Z","messageCount":2,"participants":["Ian Katz","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"77398","messageId":"dc5b80bf0805210942l388c4439g84b8a6b02346ebe8@mail.gmail.com","threadId":"13603","inReplyTo":null,"subject":"git tutorial","fromName":"Ian Katz","fromEmail":"ifreecarve@gmail.com","sentAt":"2008-05-21T16:42:33Z","receivedAt":"2008-05-21T16:42:33Z","isPatch":false,"sender":{"key":"ifreecarve@gmail.com","avatar":null},"body":"Hi Guys-\n\nI have a suggestion/request for the git documentation (tutorial),\ncurrently accessible from:\nhttp://www.kernel.org/pub/software/scm/git/docs/tutorial.html\n\nIt would be much easier to understand the \"Using git for\ncollaboration\" section if you put the username (bob or alice) as a\nprefix to each of the example command prompts, as is common in most\nlinux distributions.  This would make it easier to see at a glance who\nis doing what.\n\nIn other words, it would change from this:\n$ git clone /home/alice/project myrepo\n$ git pull /home/bob/myrepo master\n\nto this:\nbob$ git clone /home/alice/project myrepo\nalice$ git pull /home/bob/myrepo master\n\nIn the tutorial's current form, I spent so much time looking back into\nthe paragraph text to find out who was typing each command that I\neventually printed it out so I could scribble their names on each one.\n\nI hope this change isn't a big deal.\n\nThanks,\n-Ian\n"},{"id":"77450","messageId":"alpine.DEB.1.00.0805221030380.30431@racer","threadId":"13603","inReplyTo":"dc5b80bf0805210942l388c4439g84b8a6b02346ebe8@mail.gmail.com","subject":"Re: git tutorial","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-05-22T09:35:49Z","receivedAt":"2008-05-22T09:35:49Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 21 May 2008, Ian Katz wrote:\n\n> I have a suggestion/request for the git documentation (tutorial),\n> currently accessible from:\n> http://www.kernel.org/pub/software/scm/git/docs/tutorial.html\n> \n> It would be much easier to understand the \"Using git for\n> collaboration\" section if you put the username (bob or alice) as a\n> prefix to each of the example command prompts, as is common in most\n> linux distributions.  This would make it easier to see at a glance who\n> is doing what.\n> \n> In other words, it would change from this:\n> $ git clone /home/alice/project myrepo\n> $ git pull /home/bob/myrepo master\n> \n> to this:\n> bob$ git clone /home/alice/project myrepo\n> alice$ git pull /home/bob/myrepo master\n> \n> In the tutorial's current form, I spent so much time looking back into\n> the paragraph text to find out who was typing each command that I\n> eventually printed it out so I could scribble their names on each one.\n\nThis is a good change, yes.\n\n> I hope this change isn't a big deal.\n\nHey, why don't you give it a try?\n\nJust\n\nIan$ git clone git://git.kernel.org/pub/scm/git/git.git\nIan$ cd git\nIan$ $EDITOR Documentation/tutorial.txt\n\t# make the suggested changes\n\nIan$ git config user.name \"Ian Katz\"\nIan$ git config user.email ifreecarve@gmail.com\nIan$ git commit -s Documentation/tutorial.txt\n\t# write a nice oneline description, such as\n\t#    tutorial: prefix the prompts with the names \"alice\" or \"bob\"\n\t# then an empty line and then a paragraph as to why you like this\n\t# change\n\nIan$ git format-patch -1\n\t# then send the file 0001-*.patch, but inline, please\n\nHmm?\n\nCiao,\nDscho\n"}]}