UI nitpick · Han-Wen Nienhuys <hidden> · 2016-08-11
[PATCH] git-reset --hard: tell the user what the HEAD was reset to · Johannes Schindelin <hidden> · 2016-06-15
Re: [PATCH] git-reset --hard: tell the user what the HEAD was reset to · Andy Whitcroft <hidden> · 2016-06-15
Re: [PATCH] git-reset --hard: tell the user what the HEAD was reset to · Johannes Schindelin <hidden> · 2016-06-15
Re: [PATCH] git-reset --hard: tell the user what the HEAD was reset to · Andy Whitcroft <hidden> · 2016-06-15

UI nitpick

From: Han-Wen Nienhuys <hidden>
Date: 2016-08-11 20:12:27

Hi,

git-reset is really neat when you messed something up, but it 
spews messages.

  [lilydev@haring lilypond]$ git-reset  HEAD
  lily/accidental-engraver.cc: needs update
  lily/lyric-combine-music-iterator.cc: needs update

this makes me think that the reset was unsuccesful.

After a few more experiments with 

  git-reset <stuff> HEAD^ 

I started noticing that the list grew longer and longer.


It would be nice if git-reset printed 

 HEAD is now <sha1> - <excerpt of commit message>


-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help