| Summary: | Blend URL with diff: Diff is not applied but modified | ||
|---|---|---|---|
| Product: | [Applications] kompare | Reporter: | bastikln |
| Component: | general | Assignee: | Kompare developers <kompare-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kdebugzilla, sander, tibirna |
| Priority: | NOR | ||
| Version: | 4.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
bastikln
2009-12-09 17:50:58 UTC
Same here, diff file is overwritten instead of the source file. Also seems to act in reverse. Applying hunks actually UNapplies them in the right pane. Also in the hunk panel it says that the change has been undone. Same here, running Ubuntu Lucid (GNOME). From kompare --version: Qt: 4.6.2 KDE Development Platform: 4.4.2 (KDE 4.4.2) Kompare: 4.0.0 I've been starting with `kompare -b foo_dir/ /path/to/diff/of/foo/on/different/branch.patch` Is there anything new on this? I can still see the bug with Kompare 4.0. This (applying a patch to a directory), btw is a huge feature with git and, if working right, would make kompare (almost) the only graphic tool for replacing patch(1). Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Yes, kompare still unusable. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |