+1 to removing the reset. The idea was to let Gump recover when Git thinks the local copy was modifed. But this goes too much against Git's view of things. I can't see anything better than the old fashioned rm -rf
On Wednesday, April 20, 2016, Stefan Bodewig <bode...@apache.org> wrote: > On 2016-04-20, Rainer Jung wrote: > > > What was the reason for the hard reset and could we remove it until a > > better solution is found? > > I think the reason has been git not picking up the effect of changes to > .gitattributes - I'm not convinced the reset helps without removing the > index first anyway. > > Removing the reset is trivial :-) > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@gump.apache.org <javascript:;> > For additional commands, e-mail: general-h...@gump.apache.org > <javascript:;> > >
