Hi Neil,<br> Thank you so much for looking through it and providing some comments.<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> * ``bzr init myproject`` will create the myproject directory if it doesn't<br> exist, so that is the only command you need to get started. There is even a<br> --create-prefix option which is the equivalent of mkdir's -p.<br> </blockquote><div><br>NIce. :) I've changed it so that it's using a single command now. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> * If you want to show the effect of adding only specific files, you should not<br> add every file: ``bzr add build.properties build.xml``.<br> </blockquote><div><br>Good point, I modified it so it's adding bzr add build.xml and license.txt (skipping the middle one) to show the point a bit better. <br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * For ``bzr ignore`` it would be nice to show that .bzrignore now exists, is<br> added to version control and what its contents are. Also, from ``bzr help<br> ignore``, regular expressions are a killer feature for bzr ignore patterns.<br> </blockquote><div><br>Good point here as well. I updated it to include part of the "bzr help patterns" message. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * ``bzr whoami`` should include an email address, so perhaps<br> ``bzr whoami "Bob <<a href="mailto:bob@example.com">bob@example.com</a>>"``<br> </blockquote><div><br>Thanks for catching this, I was actually using "Bob <<a href="mailto:bob@example.com">bob@example.com</a>>" in the other examples, but I somehow missed that one. :) <br></div><div> </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * You may or may not want to mention (pluggable) mail client support in ``bzr<br> send``. I personally think it's pretty cool.</blockquote><div><br>I'd be very happy to add this, but hadn't gotten around to setting this up. Can you send me an example that shows the pluggableness of it?<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * If I were Bob and were reviewing someone else's changes, I would not merge<br> them into the main branch directly. Do you want to show Bob making a new<br> branch to do review in?</blockquote><div><br>I tried to explain that Bob applied the changes to his local branch, but did not show him creating it because that was done in example 2. Do you think this needs more explanation? Or perhaps I can simply reference the previous example there.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * Some people use aliases to shadow the default behavior of built-incommands.<br> ``bzr alias log="log --short -r -10.."`` for example.<br> </blockquote><div><br>Ah, I see. So you mean they use the alias to override the build in commands with a more desirable result?<br><br>This is a good point too, I'll add it as part of that example.<br><br>Thanks so much, again, for taking the time to read through it and provide comments.<br> <br>Cheers,<br>Eric <br></div></div><br clear="all"><br>-- <br>Learn from the past. Live in the present. Plan for the future.<br>11101000<br><a href="http://www.townsfolkdesigns.com/blogs/elberry">http://www.townsfolkdesigns.com/blogs/elberry</a><br>