bzr send should warn on uncommitted local changes

Bug #206577 reported by Henrik Nordström on 2008-03-25
Affects Status Importance Assigned to Milestone
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

  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> -
Jabber: <email address hidden>

Changed in bzr:
importance: Undecided → Low
status: New → Triaged
Martin Pool (mbp) wrote :

This can be done in a similar way to what push did for bug 284038.

Vincent Ladeuil (vila) on 2009-06-26
Changed in bzr:
assignee: nobody → Vincent Ladeuil (vila)
status: Triaged → Fix Committed
Vincent Ladeuil (vila) on 2009-06-29
Changed in bzr:
milestone: none → 1.17
status: Fix Committed → In Progress
Vincent Ladeuil (vila) on 2009-06-30
Changed in bzr:
status: In Progress → Fix Committed
Vincent Ladeuil (vila) on 2009-07-02
Changed in bzr:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers