'bzr merge' should require the url to be explicitly given

Bug #397253 reported by Martin Pool
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned
Breezy
Triaged
Medium
Unassigned

Bug Description

As discussed in <https://bugs.edge.launchpad.net/bzr/+bug/395906> having a default URL for the source of merge seems questionable; people don't consistently merge from one place as consistently as they may do with push and pull, and the default source may sometimes be surprising.

Tags: ui
Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 397253] [NEW] 'bzr merge' should require the url to be explicitly given

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> Public bug reported:
>
> As discussed in <https://bugs.edge.launchpad.net/bzr/+bug/395906> having
> a default URL for the source of merge seems questionable; people don't
> consistently merge from one place as consistently as they may do with
> push and pull, and the default source may sometimes be surprising.

I am very consistent about where I merge from, and I like this feature.

I think many people will be in the position of frequently merging trunk
into their feature branches, and this feature makes that easier. As
well as people using it for merging, it would also hurt those using
merge --pull.

I don't know why you say the default merge source is surprising, but I
would rather improve the selection of default merge source than disable
the feature.

I think that taking it away would make bzr harder to use.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpVfIMACgkQ0F+nu1YWqI1R4QCePk2/ktlwW6q/JwqdTz5jQ/oG
zKgAnAsf3FMw8XIcwFQEMeD8ok2RoFM0
=CyaP
-----END PGP SIGNATURE-----

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
Changed in brz:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.