On Mon, 2009-10-19 at 23:04 +0200, Krzysztof Kosiński wrote:
Here's a short outline. Ted, please correct if I got something wrong.
This looks good. There is also some generic bazaar documentation here:
http://doc.bazaar-vcs.org/latest/en/
For me, I use a slightly different workflow that I thought I'd document for folks who might be interested. It is more complex, but I like the way it works for me. I set up a shared repo and make local branches.
0. mkdir inkscape 1. bzr init-repo inkscape 2. cd inkscape 3. bzr branch lp:inkscape trunk 4. (cd trunk ; bzr bind lp:inkscape) 5. bzr branch trunk my-new-feature 6. cd my-new-feature 7. edit ; commit ; edit ; commit ; edit ; commit ; etc. 8. cd .. 9. cd trunk A. bzr merge ../my-new-feature B. <check to make sure I didn't screw something up> C. bzr commit
This allows me to have lots of "new-feature" branches, basically anytime I have an idea, but still keep things a little bit sane :)
Note that lp:inkscape is currently out of date due to an import error, but it will be fixed after the 0.47 release.
I have a test import uploaded that I think is working pretty good. I'm perfecting it, and need to get the other branches. But focusing on trunk.
lp:~ted/+junk/inkscape-trunk-import-test-2009-10-14
--Ted