Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368433 - [Client] Git log pages don't work
Summary: [Client] Git log pages don't work
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.4   Edit
Assignee: Malgorzata Janczarska CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 368569 (view as bug list)
Depends on:
Blocks: 369591
  Show dependency tree
 
Reported: 2012-01-12 05:36 EST by Malgorzata Janczarska CLA
Modified: 2012-01-26 11:31 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Malgorzata Janczarska CLA 2012-01-12 05:36:07 EST 
On git log on remote pages are not shown. On git log on local branch pages are shown but have invalid URL.
Comment 1 Szymon Brandys CLA 2012-01-16 03:59:35 EST 
*** Bug 368569 has been marked as a duplicate of this bug. ***
Comment 2 Susan McCourt CLA 2012-01-24 17:13:35 EST 
getting more frustrating these days when I'm browsing lots of git hub remotes to find commits from contributors.
Comment 3 Malgorzata Janczarska CLA 2012-01-25 03:38:53 EST 
(In reply to comment #2)
> getting more frustrating these days when I'm browsing lots of git hub remotes
> to find commits from contributors.

I know it's not convenient, but until the bug gets fixed you can change URL in the link ?page=<page number>. At least you'll get to see the next page.
Comment 4 Susan McCourt CLA 2012-01-25 11:42:19 EST 
(In reply to comment #3)
> (In reply to comment #2)
> > getting more frustrating these days when I'm browsing lots of git hub remotes
> > to find commits from contributors.
> 
> I know it's not convenient, but until the bug gets fixed you can change URL in
> the link ?page=<page number>. At least you'll get to see the next page.

yes, that's what I did...for a few seconds though I thought the contributor's repo didn't have any more pages, and then I remembered the bug.
Comment 5 Malgorzata Janczarska CLA 2012-01-26 11:31:37 EST 
The problem occurred to be both client and server side:
* we have a bug that we don't display log for branches with "/" in the name Bug 347943 and next page link for local branch contained full branch name
* on client there was a problem that in commands we wheren't operating on the log, but on the Remote, and log didn't have any pointer to the remote. I did the best to handle it, I decorated the Remote object with links to next and previous pages generated based on the log response. It would be easier if we could unify this approach.