Merge lp://qastaging/~drizzle-developers/launchpad-work-items-tracker/add-drizzle into lp://qastaging/launchpad-work-items-tracker
Proposed by
Monty Taylor
Status: | Rejected |
---|---|
Rejected by: | Martin Pitt |
Proposed branch: | lp://qastaging/~drizzle-developers/launchpad-work-items-tracker/add-drizzle |
Merge into: | lp://qastaging/launchpad-work-items-tracker |
Diff against target: |
15 lines (+11/-0) 1 file modified
config/drizzle.cfg (+11/-0) |
To merge this branch: | bzr merge lp://qastaging/~drizzle-developers/launchpad-work-items-tracker/add-drizzle |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Pitt (community) | Disapprove | ||
Review via email:
|
Commit message
Added a config file for drizzle.
Description of the change
Added a config file for drizzle. We're using it now: http://
To post a comment you must log in.
Unmerged revisions
- 238. By Monty Taylor
-
Added config for drizzle project.
Would it be okay for you to just keep your config file in your local installation? If we'd commit it to trunk, we would suddenly get the drizzle worki items on people.ubuntu.com as well.
In fact, I think we should do that the other way around - I should remove the Ubuntu/Canonical configuration files from bzr, and just keep them locally on our servers. Then they wouldn't annoy you if you run all-projects on your server. Does that sound okay?