Merge lp:~ian-clatworthy/bzr-builder/fix-find-branches into lp:~james-w/bzr-builder/trunk-old
| Status: | Work in progress |
|---|---|
| Proposed branch: | lp:~ian-clatworthy/bzr-builder/fix-find-branches |
| Merge into: | lp:~james-w/bzr-builder/trunk-old |
| Diff against target: |
22 lines (+0/-8) 1 file modified
__init__.py (+0/-8) |
| To merge this branch: | bzr merge lp:~ian-clatworthy/bzr-builder/fix-find-branches |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| James Westby | 2009-11-23 | Resubmit on 2009-11-23 | |
|
Review via email:
|
|||
| Ian Clatworthy (ian-clatworthy) wrote : | # |
| James Westby (james-w) wrote : | # |
Hi,
I have no problem with the symlink going away. However, I use
the code in the __init__.py in a pre_commit hook to test the
changes, and I don't want to use that.
After several times of trying to get this right this is the best
current approach, but clearly isn't there yet. Some way in bzr
to tell it to load a plugin from a particular directory with a
known name would allow us to avoid all of this.
Thanks,
James
| Robert Collins (lifeless) wrote : | # |
James, it would be nice if you could change the review status to 'in development' or some such when giving a review like this, otherwise it stays in the 'to review' list.
Also, please consider assigning ~bzr as a reviewer for the branch so that the whole team can help you out.
Unmerged revisions
- 55. By Ian Clatworthy on 2009-11-23
-
Delete the recursive symlink as it breaks anything relying on repo.find_
branches( ). For example, "bzr multi-pull" in my plugins directory goes into an endless loop because of this. Also, you can get easy testing via something like "bzr selftest bp.builder" IIUIC.

This patch deletes the recursive symlink under plugins/builder. It causes pain and isn't needed. See the commit message for details.