bzr send should warn on uncommitted local changes
Bug #206577 reported by
Henrik Nordström
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Low
|
Vincent Ladeuil | ||
Bug Description
bzr send without revision specification should reject or at least warn the user if there is uncommitted changes in the local working tree. It's very unlikely the user intended to send the bundle without the local modifications included, and can result in a lot of confusion if silently ignored.
Related branches
lp:~vila/bzr/206577-send-strict
- John A Meinel: Approve
- Diff: 397 lines
lp:~vila/bzr/integration
- Vincent Ladeuil: Approve
-
Diff: 31 lines (+4/-4)2 files modifiedbzrlib/lazy_regex.py (+3/-3)
doc/en/release-notes/bzr-2.7.txt (+1/-1)
Revision history for this message
| Jelmer Vernooij (jelmer) wrote Re: [Bug 206577] [NEW] bzr send should warn on uncommitted local changes | #1 |
| Changed in bzr: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Martin Pool (mbp) wrote | #2 |
| Changed in bzr: | |
| assignee: | nobody → Vincent Ladeuil (vila) |
| status: | Triaged → Fix Committed |
| Changed in bzr: | |
| milestone: | none → 1.17 |
| status: | Fix Committed → In Progress |
| Changed in bzr: | |
| status: | In Progress → Fix Committed |
| Changed in bzr: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
status triaged
importance low
I agree. It also makes a lot of sense when novice users don't know that
"bzr send" requires "bzr commit".
--
Jelmer Vernooij <email address hidden> - http://
Jabber: <email address hidden>