Pipes with reserved names can be created
Bug #657312 reported by
Jelmer Vernooij
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bzr-pipeline |
Fix Released
|
Low
|
Unassigned | ||
| bzr-pipeline (Debian) |
Fix Released
|
Unknown
|
|||
Bug Description
Ben Finney in Debian bug 574682 reported that he (while trying to figure out how to use bzr-pipeline) was able to create pipes with special names, e.g. he manages to do "bzr add-pipe --after :prev".
Obviously this isn't very common, but it'd be nice if bzr-pipeline would refuse creating pipes with reserved names to avoid user confusion.
| Changed in bzr-pipeline (Debian): | |
| status: | Unknown → New |
| Changed in bzr-pipeline (Debian): | |
| status: | New → Confirmed |
| Changed in bzr-pipeline: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Aaron Bentley (abentley) wrote | #1 |
| Changed in bzr-pipeline: | |
| status: | Triaged → Fix Released |
| Changed in bzr-pipeline (Debian): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
add-pipeline now treats :prev and :next as aliases, so it refuses to create a pipe named :prev or :next.