Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344050 - [client] support "revert to remote version" or "git log" on git status page
Summary: [client] support "revert to remote version" or "git log" on git status page
Status: CLOSED DUPLICATE of bug 344280
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 17:43 EDT by Susan McCourt CLA
Modified: 2011-08-30 10:21 EDT (History)
1 user (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 Susan McCourt CLA 2011-04-27 17:43:31 EDT 
Today I've been trying to exclusively use orion git support rather than my command line and git gui tools.

One thing I have to keep returning to the command line/gui tools for is backing out of a change I made that I don't want anymore.  In Git GUI, I can select an unstaged change and choose "revert" which will restore me back to the remote version.  Very convenient.

Presumably the way I would do this today in Orion is go to the git log page for that file and then fetch the revision I want?  (I can't get git log for a specific file working due to bug 344038).

It would be nice to have some way to start this workflow from git-status, because that is where I notice that I have a change that's bogus.  Either "revert to remote version" as a command or a command that takes to me to git log for that file.
Comment 1 John Arthorne CLA 2011-04-28 10:00:14 EDT 
To be clear, this is about reverting an *unstaged* change ("Replace with File in Git Index" is the command name in eGit).  Bug 343963 is about reverting a change that was commited but not pushed. Both are useful, just wanted to make sure the bugs are clear.
Comment 2 Susan McCourt CLA 2011-04-28 10:52:12 EDT 
(In reply to comment #1)
> To be clear, this is about reverting an *unstaged* change ("Replace with File
> in Git Index" is the command name in eGit).  Bug 343963 is about reverting a
> change that was commited but not pushed. Both are useful, just wanted to make
> sure the bugs are clear.

Yes.  For my workflows, this case is much more common than the other bug.  I often make experimental or debug changes and then want to toss them.
Comment 3 Susan McCourt CLA 2011-05-02 11:53:40 EDT 
marking duplicate of newer bug because that one is assigned.

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