Point users to correct way of submitting patches
Bug #299809 reported by
Jonathan Lange
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
More than once I've had to ask a project maintainer how they'd like to receive the branches/patches I've written, even though their project is on Launchpad.
The problem is that a project might use Launchpad for hosting code, but still want to use a different method for handling merge requests (Bazaar, for example, will have to have BundleBuggy pried from its cold dead fingers).
There should be a way to help users find out:
- whether their merge proposal is likely to be looked at ever.
- how they should best submit patches.
Changed in launchpad-bazaar: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
To post a comment you must log in.