Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 371418 - repositories page - find myself surprised when commits list pops in
Summary: repositories page - find myself surprised when commits list pops in
Status: RESOLVED DUPLICATE of bug 369605
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-13 14:53 EST by Susan McCourt CLA
Modified: 2012-02-14 04:00 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2012-02-13 14:53:38 EST
(note this is a post 0.4 issue)...

Several times today I'm creating topic branches as I review late-breaking changes for RC1 and RC2.  I find that the workflow for branches is pretty good on the repo page.  But when I switch branches, the commits page fills in with a bunch of commits and I lose my context completely.  So I have to go find the branch list again.

Since commits are so easily seen in git log, I wonder if we should be quite conservative about showing them here.  Maybe only show if you click View All?  I don't think we should assume that someone wants the commit list when they are manipulating branches.  For things like checkout/rebase scenarios the commits are just noise until I'm done and ready to look at something.
Comment 1 Szymon Brandys CLA 2012-02-14 04:00:19 EST
I do merge and rebase from the repository page and I find it very useful. Switching to the log page from the repo page just to do merge does not make sense to me. Moreover you have to use 2 git log pages to show the same info you see on the repo page i.e. see both incoming and outgoing changes.

There is already bug raised by you to keep your position when you make changes on the repo page.

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