Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • meld meld
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 197
    • Issues 197
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • meldmeld
  • Issues
  • #44
Closed
Open
Issue created May 15, 2012 by Bugzilla@bugzilla-migration💬Reporter

[BZ#676104] Show diff between common ancestor and conflicting children

Submitted by Sami Wagiaalla

Link to original bug (#676104)

Description

I have diff3 enabled in my .gitconfig:

[merge] conflictstyle=diff3

Which meld seems to be handling correctly. It would be really cool however if meld would show me what has changed remotely that is causing the conflict.

For example in the attached image I had moved a chunk of code to its own function. Someone changed this code remotely but I could not tell what the change was even though I was looking at the remote version(left) vs the common ancestor(center). When I copied the code to files ran diff I found this:

  • setProjectRoot(FedoraPackagerUtils.getProjectRoot(eventResource));
  • setProjectRoot(FedoraPackagerUtils
  •             .getProjectRoot(eventResource));

:)

If meld highlighted this in a darker red that would be great! You do this in the blue non conflicting changes.

Thanks

Assignee
Assign to
Time tracking