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

Bug #475451 reported by GuilhemBichot on 2009-11-05
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Ian Clatworthy

Bug Description

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.

Related branches

summary: - please mention in "bzr help diff" that -c gives diff against *left*
- parent
+ MYSQL/BZR P3: please mention in "bzr help diff" that -c gives diff
+ against *left* parent
description: updated
visibility: public → private

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) wrote :

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

Martin Pool (mbp) on 2009-11-17
Changed in bzr:
status: New → Confirmed
importance: Undecided → Medium
tags: added: doc easy
visibility: private → public
Changed in bzr:
status: Confirmed → Fix Committed
assignee: nobody → Ian Clatworthy (ian-clatworthy)
GuilhemBichot (guilhem-bichot) wrote :

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

John A Meinel (jameinel) on 2009-11-30
Changed in bzr:
milestone: none → 2.1.0b4
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