'bzr merge -h' should explain how to octopus merge
Bug #481526 reported by
Ian Clatworthy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Bazaar supports merges with more than 2 parents but the help for merge explicitly states merging is a 2 parent operation. We need to mention the multi-parent capability and give the actual procedure to use. I *think* it's something like:
bzr merge ../parent1
bzr merge ../parent2 --force
but I'm not completely sure. FWIW, I want this improved so that Stephen Turnbull's Bazaar for Git Users document can reference it.
Related branches
lp://staging/~nmb/bzr/fix-481526
Merged
into
lp://staging/bzr
- Vincent Ladeuil: Approve
-
Diff: 48 lines (+15/-0)2 files modifiedNEWS (+3/-0)
bzrlib/builtins.py (+12/-0)
Changed in bzr: | |
status: | Confirmed → Fix Released |
milestone: | none → 2.1.0rc1 |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ian Clatworthy wrote:
> Public bug reported:
>
> Bazaar supports merges with more than 2 parents but the help for merge
> explicitly states merging is a 2 parent operation. We need to mention
> the multi-parent capability and give the actual procedure to use. I
> *think* it's something like:
>
> bzr merge ../parent1
> bzr merge ../parent2 --force
>
> but I'm not completely sure. FWIW, I want this improved so that Stephen
> Turnbull's Bazaar for Git Users document can reference it.
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>
>
> ** Tags: doc
>
importance medium
status confirmed
That is generally how it is done. However the *merge* action *is* a
2-parent operation. At least, I think the second merge will use a
common ancestor based on 2 revisions (I don't think we use 'parent1' to
determine the common ancestor.)
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkr 8c90ACgkQJdeBCY SNAANTBQCgx0RXJ LxHU/noULQEyWsl QwF1 2ITsmtXH36cnDA3 cA
ov0AoLnOhxXosk+
=UHFg
-----END PGP SIGNATURE-----