Re: Bazaar configuration
Sorry for jumping into this thread so late in the game... On Mar 29, 4:47 pm, plumpy plu...@gmail.com wrote: The way we have it set up here is that the repository configured in Review Board is the URL that contains the .bzr directory. In your case, this looks like probablyhttp://a.org/~lead/projects/my_proj_mainline Now if you're diffing against that directory directly, you'd use '/' as your base diff path. Two notes: * theBazaarcode that Ben wrote works a lot better if you have the bzr-diff-revid plugin installed. By default, 'bzr diff' doesn't really give enough information in the diff header to accurately identify that original version. The bzr-diff-revid plugin fixes that. You can install it by cd'ing into yourbazaarplugins directory (~/.bazaar/ plugins on UNIX or ~/Application Data\bazaar\2.0\plugins on Windows) and doing 'bzr co lp:bzr-diff-revid diff_revid'. Why not use bzr send? It should have everything you need? Also, I didn't see a BazaarClient in post-review... is that intentional, or was there just no need for it? Thanks! -John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Bazaar configuration
The way we have it set up here is that the repository configured in Review Board is the URL that contains the .bzr directory. In your case, this looks like probably http://a.org/~lead/projects/my_proj_mainline Now if you're diffing against that directory directly, you'd use '/' as your base diff path. Two notes: * the Bazaar code that Ben wrote works a lot better if you have the bzr-diff-revid plugin installed. By default, 'bzr diff' doesn't really give enough information in the diff header to accurately identify that original version. The bzr-diff-revid plugin fixes that. You can install it by cd'ing into your bazaar plugins directory (~/.bazaar/ plugins on UNIX or ~/Application Data\bazaar\2.0\plugins on Windows) and doing 'bzr co lp:bzr-diff-revid diff_revid'. * If you have a branch of my_proj_mainline on a developer box and you want to create a diff of the local commits since you last pushed up to the main branch, you can do 'bzr diff -r submit:'. (It'll work the way you're doing it, too, obviously, but the '-r submit:' method doesn't require two different branches. If you still have problems, maybe you can give me a stack trace or something. Or at least some better description of the problems you're seeing. Thanks, Michael P. On Mar 28, 8:12 pm, Prabhu Ramachandran pra...@aero.iitb.ac.in wrote: Hi Christian, On 03/29/09 02:24, Christian Hammond wrote: Would you mind sharing your configuration (or at least a representation of it) and how you manage updates to the repository, etc? Something we could use as a basis for docs. Sure, it was pretty simple. Here is perhaps a rambling overview of how I use it. I am not sure this is optimal. I hope it helps. cheers, prabhu Development with BZR -- Bazaar is a DVCS. Imagine a setup where there are several developers working on a common project. Each developer maintains an independent branch on which they develop whatever feature they want. They then copy (via rsync/scp or make a symbolic link) their repositories over to their web page, say ``http://a.org/~developer/projects/my_proj`` One of the developers (the lead say) maintains a mainline or official branch which is also exposed on his web page say ``http://a.org/~lead/projects/my_proj_mainline`` Each developer maintains an up-to-date copy of mainline on their machine. Usually this is achieved with a pull like so:: cd my_proj_mainline bzr pullhttp://a.org/~lead/projects/my_proj_mainline Now when the developer is happy with a branch and wants to commit to the mainline they make a diff between the mainline and their branch like so:: cd my_proj bzr diff --old ../my_proj_mainline cool_new_feature.diff Upload this patch to the Review Board site. Setting up Review Board First make sure you are using a recent enough version of bzr. 1.12 works fine with review board's bzr scmtool. Add a new repository as follows: 1. Set the Name of the project, ``my_proj`` in this case. 2. Set the mainline project url to the repository as: ``http://a.org/~lead/projects/my_proj_mainline`` 3. Set the tool to Bazaar. 4. Make any other settings and add the new repository. You're all set. Using review board --- This is pretty standard. Just login, create a new review request, upload your diff ``cool_new_feature.diff``, and set the base directory to ``/`` (which works in my case). Fill in the necessary fields and you should be set for a review. Once the reviewers have approved the diff, someone (the lead usually) applies the diff to mainline and others update their branches and pull from mainline on their official copy. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Bazaar configuration
On 24. mar. 2009, at 03.01, Christian Hammond wrote: Hi, I don't really know anything about the Bazaar support, having no experience with Bazaar. I'd definitely have written up some docs about it otherwise, and would like to if someone will explain the setup to me. The people who would know are Henrik Hedberg and Ben Jansen, so I'm CCing them on this. Can you guys go over your configuration, give us some tips and info we could put in the docs? No new feedback on this? I could help with documentation or whatever, if I only had any pointers as to how it's supposed to work. Review Board looks like a really great tool, but this is currently preventing us from using it. :( Regards, Anders Steinlein --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Bazaar configuration
Hi Prabhu, Would you mind sharing your configuration (or at least a representation of it) and how you manage updates to the repository, etc? Something we could use as a basis for docs. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.review-board.org VMware, Inc. - http://www.vmware.com On Sat, Mar 28, 2009 at 9:24 AM, Prabhu Ramachandran pra...@aero.iitb.ac.in wrote: On 03/28/09 16:15, Anders Steinlein wrote: I don't really know anything about the Bazaar support, having no experience with Bazaar. I'd definitely have written up some docs about it otherwise, and would like to if someone will explain the setup to me. The people who would know are Henrik Hedberg and Ben Jansen, so I'm CCing them on this. Can you guys go over your configuration, give us some tips and info we could put in the docs? No new feedback on this? I could help with documentation or whatever, if I only had any pointers as to how it's supposed to work. Review Board looks like a really great tool, but this is currently preventing us from using it. :( I have a reviewboard setup that works with bzr and the only thing I needed to do was to upgrade the server to use the latest bzr release (1.12). Maybe that would help? cheers, prabhu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Bazaar configuration
Hi Christian, On 03/29/09 02:24, Christian Hammond wrote: Would you mind sharing your configuration (or at least a representation of it) and how you manage updates to the repository, etc? Something we could use as a basis for docs. Sure, it was pretty simple. Here is perhaps a rambling overview of how I use it. I am not sure this is optimal. I hope it helps. cheers, prabhu Development with BZR -- Bazaar is a DVCS. Imagine a setup where there are several developers working on a common project. Each developer maintains an independent branch on which they develop whatever feature they want. They then copy (via rsync/scp or make a symbolic link) their repositories over to their web page, say ``http://a.org/~developer/projects/my_proj`` One of the developers (the lead say) maintains a mainline or official branch which is also exposed on his web page say ``http://a.org/~lead/projects/my_proj_mainline`` Each developer maintains an up-to-date copy of mainline on their machine. Usually this is achieved with a pull like so:: cd my_proj_mainline bzr pull http://a.org/~lead/projects/my_proj_mainline Now when the developer is happy with a branch and wants to commit to the mainline they make a diff between the mainline and their branch like so:: cd my_proj bzr diff --old ../my_proj_mainline cool_new_feature.diff Upload this patch to the Review Board site. Setting up Review Board First make sure you are using a recent enough version of bzr. 1.12 works fine with review board's bzr scmtool. Add a new repository as follows: 1. Set the Name of the project, ``my_proj`` in this case. 2. Set the mainline project url to the repository as: ``http://a.org/~lead/projects/my_proj_mainline`` 3. Set the tool to Bazaar. 4. Make any other settings and add the new repository. You're all set. Using review board --- This is pretty standard. Just login, create a new review request, upload your diff ``cool_new_feature.diff``, and set the base directory to ``/`` (which works in my case). Fill in the necessary fields and you should be set for a review. Once the reviewers have approved the diff, someone (the lead usually) applies the diff to mainline and others update their branches and pull from mainline on their official copy. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Bazaar configuration
I can't for the life of me get diffs from a Bazaar repo to work. Quite possibly because I'm walking in the dark when it comes to configuring the repo, as the documentation (which, by the way, is generally very good now) makes no mention of how to register a Bazaar repo. How exactly should this be configured? What should the path point to? A branch with a working tree, or a shared repository with containing branches? Or maybe even the .bzr directory? And when submitting a review request in the web UI, what should the base diff path be? The documentations seems to suggest that this is only relevant for Subversion. I have tried many different options (one example: pointing to a shared repository without working trees and base diff path to the branch within), but to no avail. Uploading the diff gives me no error, but attempting to view the diff simply presents a blank page. Any pointers would be much appreciated. Regards, Anders Steinlein --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Bazaar configuration
Hi, I don't really know anything about the Bazaar support, having no experience with Bazaar. I'd definitely have written up some docs about it otherwise, and would like to if someone will explain the setup to me. The people who would know are Henrik Hedberg and Ben Jansen, so I'm CCing them on this. Can you guys go over your configuration, give us some tips and info we could put in the docs? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.review-board.org VMware, Inc. - http://www.vmware.com On Sun, Mar 22, 2009 at 11:33 PM, Anders Steinlein and...@steinlein.nowrote: I can't for the life of me get diffs from a Bazaar repo to work. Quite possibly because I'm walking in the dark when it comes to configuring the repo, as the documentation (which, by the way, is generally very good now) makes no mention of how to register a Bazaar repo. How exactly should this be configured? What should the path point to? A branch with a working tree, or a shared repository with containing branches? Or maybe even the .bzr directory? And when submitting a review request in the web UI, what should the base diff path be? The documentations seems to suggest that this is only relevant for Subversion. I have tried many different options (one example: pointing to a shared repository without working trees and base diff path to the branch within), but to no avail. Uploading the diff gives me no error, but attempting to view the diff simply presents a blank page. Any pointers would be much appreciated. Regards, Anders Steinlein --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
