| AtomicSpark | Anyone awake? :) | 09:54 |
|---|---|---|
| jpds | AtomicSpark: Possibly. | 09:56 |
| AtomicSpark | Ha. You tricksters! I was trying to grab the bzr of the server guide and the wiki's example was for kubuntu. :3 | 09:58 |
| AtomicSpark | It's way too late/early to be that observant. | 09:58 |
| AtomicSpark | So the wiki says I can edit something and then submit it? Does that mean there is a public upload access that is... reviewed? | 09:59 |
| jpds | AtomicSpark: Bzr branches for the ubuntu-docs are at https://code.edge.launchpad.net/ubuntu-docs | 10:01 |
| jpds | AtomicSpark: Which wiki are you referring to? | 10:02 |
| AtomicSpark | Yes I found that. Just removed the 'k' ;) | 10:02 |
| AtomicSpark | Somewhere around https://wiki.ubuntu.com/DocumentationTeam/Mentoring | 10:02 |
| jpds | bzr branches → reviewed, wiki.u.c → open to edits from all. | 10:03 |
| AtomicSpark | so how do i submit my edit for review? do i just bzr update? | 10:04 |
| * AtomicSpark isn't used to bzr | 10:05 | |
| jpds | AtomicSpark: http://doc.bazaar.canonical.com/bzr.2.0/en/tutorials/using_bazaar_with_launchpad.html | 10:05 |
| AtomicSpark | i figured update was one way. just updated my local checkout. | 10:05 |
| jpds | AtomicSpark: I suggest you read: http://doc.bazaar.canonical.com/bzr.2.0/en/mini-tutorial/index.html too. | 10:07 |
| AtomicSpark | My question is more what to do, rather than how to use bzr. Am I supposed to checkout the file I want to work on and then push for review? Or is that type of access only avalable to members? | 10:08 |
| jpds | AtomicSpark: You have to push it to a separate branch on Launchpad and then submit a merge proposal for it. | 10:09 |
| AtomicSpark | Hmm. | 10:09 |
| jpds | AtomicSpark: An example of mine being: https://code.edge.launchpad.net/~jpds/launchpad/fix_176396/+merge/16082 | 10:09 |
| AtomicSpark | That makes sense. | 10:11 |
| jpds | (This one is for launchpad though, not the docs.) | 10:11 |
| AtomicSpark | In theory, it's the same thing. :) | 10:11 |
| jpds | Yep. | 10:11 |
| AtomicSpark | Do i need to retain the paths of the original branch? Let's say I want to edit karmic/serverguide/C/file.xml, do I need to have the path karmic/serverguide/C in my branch? or just the file.xml? | 10:20 |
| jpds | Either one. :) | 10:20 |
| jpds | AtomicSpark: Did you create your own branch first by branching lp:ubuntu-docs? | 10:21 |
| AtomicSpark | Yes. | 10:21 |
| jpds | Groovy. | 10:22 |
| AtomicSpark | I was just going to create another and just copy the relevant file over. | 10:22 |
| === ZachK_ is now known as Guest13017 | ||
| jpds | AtomicSpark: You can do that with: bzr branch ubuntu-docs my-branches-for-changes . | 10:22 |
| AtomicSpark | jpds: So I assume you find it easier to have a global launchpad project and just do individual branches for bugs? probably is the easiest way to go about it. might even be de facto! | 10:44 |
| === astechgeek is now known as techgeek | ||
| === astechgeek is now known as techgeek | ||
| === Pendulum_ is now known as Pendulum | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!