dpush should behave identically to push

Bug #438158 reported by Levi Bard on 2009-09-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Vincent Ladeuil

Bug Description

As far as it makes sense, dpush should present an identical UI to push's.
For example, it should honor strict/no-strict and default to the same behavior when a branch has uncommitted changes.

Related branches

Vincent Ladeuil (vila) wrote :

So looking at push options not proposed by dpush as of today:

--stacked, --stacked-on: Do not apply to other VCS

--create=prefix, --use-existing-dir doesn't apply to dpush AFAICS

--overwrite may apply but I have some doubts here, I understand dpush as a way to push back contributions
  to the upstream project but not to take over the trunk history so I think we don't want to support --overwrite.

That leaves --strict and I think we should restrict that bug to this option handling only.

Feel free file another bug for --overwrite if you think it's worth it.

Changed in bzr:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Vincent Ladeuil (vila)

Just handling strict/no-strict is fine with me - that was the thing I initially noticed.
I wasn't sure if some of the other things like overwrite may have been applicable to other VCSs.

Vincent Ladeuil (vila) on 2009-10-02
Changed in bzr:
status: Confirmed → Fix Committed
milestone: none → 2.1.0b1
Vincent Ladeuil (vila) on 2009-10-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