| Summary: | [client] support "revert to remote version" or "git log" on git status page | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Client | Assignee: | Project Inbox <e4.orion-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | libingw |
| Version: | 0.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Susan McCourt
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.
(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. marking duplicate of newer bug because that one is assigned. *** This bug has been marked as a duplicate of bug 344280 *** |