Looks like --amend create commit... don't understand

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Looks like --amend create commit... don't understand

From: mat <hidden>
Date: 2016-06-15 22:48:21

Hi

Sorry for this question that might appear soo simple but I'm a little 
bit lost :-(

When editing my code, I like to --amend it a lot between bigger commits. 
But when looking on gitk, I see that
git commit blabla --amend

does create each and every time a new commit, I mean: with git log, 
there is only one commit, but on gitk, I see many, with the same name 
but different revision ID.... My understanding was that it would only 
replace, not create each time a new revision.. Could you please explain 
me where Iàm wrong and what is happening exactly?

Furthermore, if I wish to delete all those intermediary amend commit, 
can I do it? If yes, how?

Thanks a lot for this help!

Matthieu

Re: Looks like --amend create commit... don't understand

From: Octavio Alvarez <hidden>
Date: 2016-06-15 22:48:21

On Wed, 24 Feb 2010 13:27:32 -0800, mat [off-list ref] wrote:
I mean: with git log, there is only one commit, but on gitk, I see many,  
with the same name but different revision ID.... My understanding was  
that it would only replace, not create each time a new revision.. Could  
you please explain me where Iàm wrong and what is happening exactly?
Try doing "reload" (as opposed to just "update") using CTRL+F5 after you
amend in order to see only the new commits, and ignore the old ones. If
you have an old version of gitk, you might need to do it directly from
the menu.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help