MYSQL/BZR P3: please mention in "bzr help diff" that -c gives diff against *left* parent

[GuilhemBichot]

This is a Sun/MySQL - Canonical escalation imported into Launchpad by the Canonical Support Team (internal case 6613 )

Original escalation: 2009-11-16 10:12 UTC

When a revision (revno X) is a merge revision, "bzr diff -c X" prints the diff against the leftmost parent (the first parent from the top in "bzr log -rX"). This can be misleading and can seem arbitrary. The proper way here is to use "bzr diff -r<chosen_parent>..X".
Could you please consider those ideas, to help the user:
- mention in "bzr help diff" that for a merge revision, -c is against the first parent, and -r<chosen_parent>..X should be used if you want a non-first parent to be used.
- or make -c fail if the revision is a merge revision (no result instead of arbitrary result), returning an error message.
Thank you.

[Robert Collins (lifeless)]

Dragomir, this bug is already closed, if MySQL want it open again,
please do reopen it.

Its also very odd to make it private when it was filed by Mysql as a
normal public bug - non staff have already seen it and seen the
discussion. I think it only makes sense to make a public bug become
private when private details are going to be discussed.

-Rob

[Robert Collins (lifeless)]

On Tue, 2009-11-17 at 04:50 +0000, Robert Collins wrote:
> Dragomir, this bug is already closed, if MySQL want it open again,
> please do reopen it.
>
> Its also very odd to make it private when it was filed by Mysql as a
> normal public bug - non staff have already seen it and seen the
> discussion. I think it only makes sense to make a public bug become
> private when private details are going to be discussed.

BAH, I sent this to the wrong bug. Still, the privacy stuff applies here
too.

-Rob

[GuilhemBichot (guilhem-bichot)]

Thanks Ian! I looked at your branch and the message is fine.