Yes, that might be the cause. Then, you can discard the last commit with git reset --hard HEAD^ or create an empty commit with git commit --allow-empty
William Seiti Mizuta @williammizuta Caelum | Ensino e Inovação www.caelum.com.br On Tue, Oct 22, 2013 at 2:55 PM, Vicki Kozel <vickiko...@gmail.com> wrote: > Also, my file on the branch that I am amending looks exactly like the file > in master. I checked their SHA1 signatures with git hash-object command - > they are identical. Maybe that what is causing the problem? > > > On Tuesday, October 22, 2013 11:53:25 AM UTC-7, Vicki Kozel wrote: >> >> Thank you William, >> I just tried that - same outcome. >> Vicki >> >> On Tuesday, October 22, 2013 11:24:29 AM UTC-7, William Seiti Mizuta >> wrote: >>> >>> >>> On Tue, Oct 22, 2013 at 2:20 PM, Vicki Kozel <vicki...@gmail.com> wrote: >>> >>>> git commit COMMON/pom.xml --amend >>> >>> >>> You don't need to pass the file in commit command. You just need to use >>> "git commit --amend" >>> >>> >>> William Seiti Mizuta >>> @williammizuta >>> Caelum | Ensino e Inovação >>> www.caelum.com.br >>> >> -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
