The quick start card is actually a quick reference card

[Clemens Tolboom]

The Card is not helping as a quick start but is more a quick reference.

Furthermore I changed the 'Inititalization' block.

bzr branch mp myproject
into
bzr branch myproject newproject

bzr checkout mp project
into
bzr checkout srcproject myproject

same for --lightweight

[Clemens Tolboom (clemens-build2be)]

This is the link http://doc.bazaar-vcs.org/bzr.dev/en/quick-reference/quick-start-summary.pdf to the document.

And I'm lost with bzr branch --help which is stating FROM-LOCATION TO-LOCATION

[Clemens Tolboom (clemens-build2be)]

hmmm ... it seems that for the file:// protocol it needs this

 bzr branch ./myproject ./newproject

So documentation change is OK :-)

[Martin Pool (mbp)]

Needs review/merge.

[John A Meinel (jameinel)]

Actual link now:
http://doc.bazaar.canonical.com/bzr.dev/en/_static/en/bzr-en-quick-reference.pdf

[John A Meinel (jameinel)]

This is the old 'quick-ref.png' file that was created.

[John A Meinel (jameinel)]

This is the new quick-reference after applying the changes.

[John A Meinel (jameinel)]

I deleted the last one, because it re-uploaded the old content. Trying again with the new .png. Unfortunately it is a lot bigger (600kb vs 200kb). I wonder if something changed with the toolchain that it doesn't optimize as much.

[John A Meinel (jameinel)]

I noticed "bazaar.canonical.com" was overflowing the right side of the page. So I tweaked the offsets. This is my 'final offer'

[John A Meinel (jameinel)]

Martin, how did you generate it? I used the "make" tool as written in the Makefile. I'd like to make sure we don't have to do a lot of steps to go from the .svg to the final .png in the tree. (We version it so that people don't have to have svg tools to build bzr, but it was nice for *me* to not have to think about how I wanted to generate the .png and .pdf)

[Martin Packman (gz)]

Yeah, manually I'm afraid. I could update the makefile to use something more capable than rsvg (and more maintained?) but those are all giant dependencies we probably want to avoid. The way the image is currently presented, I expect most people will be presented with it on a white background anyway so that and the ~200KiB probably aren't the end of the world.