[RFC] [MERGE] Draft 2 of revised mini-tutorial

Ian Clatworthy ian.clatworthy at internode.on.net
Mon Oct 15 08:18:37 BST 2007


Matthew Revell wrote:
> Thanks, look forward to your input.

bb: tweak

Some comments ...

In Introduction:

  -take a look at our guide, Learning More.
  +take a look at Learning more.

In Installation:

  - installation instructions at:
  + installation instructions below:

In Introducing yourself, either don't mention .bazaar/bazaar.conf or
note that it's a different location for Windows users.

In Putting files under version control, you need a note for Windows
users explaining what touch does so they can do the same using 'New
file' in Windows Explorer, say. Also, I'm 99% sure that U.S. spelling is
the policy in our user docs so "initialise" -> "initialize".

For Publishing Your Branch, see my other email about having 2 sections
in the one doc: one for SFTP and another for LP. (BTW, if we decide to
keep multiple docs, then the Makefile needs changes as well, or the 2nd
doc won't get converted to HTML and the link will break.)

In Merging your work, I'd like us to say that bundles have intelligent
metadata including revision history. (At the moment, we're selling them
short.)

I'm also not sure if the send command requires some configuration or
not. If it does, we need to mention that. We might also wish to add ...

"Alternatively, save the bundle to a file and email it using the tool of
your choice like this:

  bzr send -o > my-changes.patch"

In fact, if send does require some setup to email directly, I'd be
tempted to explain this way first and then explain that send can be
configured to mail directly using:

  bzr send --mail-to=...

Ian C.



More information about the bazaar mailing list