| Summary: | failed merge with no explanation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> | ||||
| Component: | Git | Assignee: | Project Inbox <orion.git-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Susan McCourt
Created attachment 204197 [details]
screenshot
I have unstaged changes so I think this is just a case of bug 356918. In bug 355549 comment 5 Tomasz said >I'm aware that the UI part can be done better, so if you don't like feel >free to open a new bug for that part. So I guess this can be that bug. Should we detect when the working tree is dirty and then guess the problem? For sure, FAILED with a warning icon leaves me thinking the problem is worse than it is. (In reply to comment #2) > Should we detect when the working tree is > dirty and then guess the problem? For 0.3 we could have the FAIL message link to a tips and tricks page. See bug 359271. *** This bug has been marked as a duplicate of bug 357860 *** |