Bug 354307 - The files changed in Code perspective after commit are closed
Summary: The files changed in Code perspective after commit are closed
Status: RESOLVED DUPLICATE of bug 354306
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: patchreview (other bugs)
Version First Reported In: git master
Platform: Mageia RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-24 14:53 UTC by Piotr Mierzwinski
Modified: 2021-10-18 00:13 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Mierzwinski 2015-10-24 14:53:36 UTC
After changing the files in Code perspective, and saving them I call review the changes. Changes look fine so I want to commit then. So I finish review calling "Finish review" (pressing properly button on "Review" view). KDevelop returning to Code perspective closes all reviewed files. This bug I reported as 354306. But now I want to commit the changes so clicking on root of project I select "Git -> Commit" and in Review perspective I press "Commit". After that KDevelop back to Code perspective but closes all changed files.

Reproducible: Always

Steps to Reproduce:
1. Start KDevelop with some project (I'm working on this: git://git.qtcmd.org/qtcmd2.git)
2. Open couple of files (let it be 5) 
3. Change couple of files (let it be 3)
4. Save them (it's no matter, might be"Save all")
5. Invoke "git -> Commit" for entire project (no matter how, for example clicking on root of project).
    In this moment Review perspective is opening.
5. Invoke "Commit"

Actual Results:  
All changed files are closed 

Expected Results:  
All changed files should be opened in Code perspective after back from Review.

KDevelop cloned in the afternoon on 2015-10-24.
Comment 1 Piotr Mierzwinski 2015-10-24 15:30:35 UTC
Sorry that I repeat myself. The same was reported by my in Bug 354141, but here (I think) description is more complete.
Comment 2 Aleix Pol 2015-10-26 00:11:42 UTC

*** This bug has been marked as a duplicate of bug 354306 ***