My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 665: Merge diff not showing for conflicts
15 people starred this issue and may be notified of changes. Back to list
Status:  Submitted
Owner:  ----
Closed:  Jun 2011

Sign in to add a comment
Reported by, Aug 18, 2010
Affected Version: 2.1.4

What steps will reproduce the problem?
1. Create a merge commit with resolved conflicts
2. Push it for code review
3. Try to click on the diff buttons on the change page

What is the expected output? What do you see instead?
Should show some kind of diff. It doesn't do anything.

Aug 18, 2010
This is a regression that was introduced in 2.1.4.
Status: Accepted
Labels: -Priority-Minor Priority-Major Milestone-2.1.5
Aug 23, 2010
(No comment was entered for this change.)
Labels: -Milestone-2.1.5 Milestone-2.1.6
Dec 8, 2010
So this was fixed in the (just released) 2.1.6? Did not see it in the release notes.
Dec 28, 2010
Version 2.1.6-rc1 also seems affected
Apr 16, 2011
Any progress on this issue for 2.1.7? It's already a long standing regression (since 2.1.4).
May 19, 2011
(No comment was entered for this change.)
Labels: -Milestone-2.1.6
Jun 24, 2011
This bug is still present in 2.2.1.
Jun 24, 2011
Of course its still present, we haven't fixed it. :-)

I'm actually trying to work on it today. Hopefully I can finish it this afternoon.
Status: Started
Jun 24, 2011
Hmm... you're really making me want to update to 2.2.x :)
Jun 24, 2011
I've hacked merges by having the server produce the automatic merge result of the parents, and then diff the actual merge result against the automatic one. A screenshot is attached showing a conflict in Gerrit Code Review's own history.
72.5 KB   View   Download
Jun 27, 2011
(No comment was entered for this change.)
Status: Submitted
Labels: FixedIn-2.2.2
Oct 25, 2011
Hello, May I know when is the 2.2.2 targeted to roll out?
Sep 10, 2012

*What steps will reproduce the problem?*
Same steps (I'm merging a branch that is managed by gerrit).

*What is the expected output? What do you see instead?*
I'm currently using version 2.3 and when I push merge commit to gerrit, I can observe two different behaviors:
* As expected, the change page shows the conflict resolution only
* The change page shows the whole merge diff (that is impossible to review: way too big)

Do you know why this second kind of behavior can happen?

Sign in to add a comment

Powered by Google Project Hosting