Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354264 - [client][status] Allow to amend commit when working tree is clean
Summary: [client][status] Allow to amend commit when working tree is clean
Status: VERIFIED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.3 M2   Edit
Assignee: libing wang CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 347029 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-09 11:04 EDT by Tomasz Zarna CLA
Modified: 2011-10-11 10:42 EDT (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 Tomasz Zarna CLA 2011-08-09 11:04:51 EDT 
Currently, you cannot amend the last commit unless there is a modified file in the working tree. When you want to amend the commit message or change author there is no way to do it.

At first I thought I will be able to change the last commit as the "Amend"message was not gray. It turned out I got fooled by bug 347029.
Comment 1 Szymon Brandys CLA 2011-08-23 10:25:20 EDT 
Who should it be assigned to?
Comment 2 libing wang CLA 2011-08-23 10:55:03 EDT 
(In reply to comment #1)
> Who should it be assigned to?

Szymon, I've assigned this to myself.
You can still assign the git-status related bugs to me if the stuff was originated by me.
Comment 3 Tomasz Zarna CLA 2011-10-05 06:27:40 EDT 
Libing, I think this one is has been already fixed, hasn't it?
Comment 4 libing wang CLA 2011-10-05 09:24:56 EDT 
(In reply to comment #3)
> Libing, I think this one is has been already fixed, hasn't it?

Yes. Just forgot to close it. Closing now.
Comment 5 Tomasz Zarna CLA 2011-10-05 10:24:26 EDT 
Verified on http://orion.eclipse.org, not sure which I-build is it. Thx.
Comment 6 libing wang CLA 2011-10-11 10:42:58 EDT 
*** Bug 347029 has been marked as a duplicate of this bug. ***