git/list[1] front-page[2] threads[3] people[4] search[5] about
 

UI nitpick

From
Han-Wen Nienhuys <hanwen@xs4all.nl>
Date
Dec 20, 2006, 22:55 UTC
Message-ID
<emcf17$esj$1@sea.gmane.org>
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
Next: Johannes Schindelin
Message 1 of 5 in “UI nitpick”
  1. Han-Wen NienhuysDec 20, 2006
  2. git-reset --hard: tell the user what the HEAD was reset toJohannes Schindelin, Dec 21, 2006
  3. Andy WhitcroftJan 3, 2007
  4. Johannes SchindelinJan 4, 2007
  5. Andy WhitcroftJan 4, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.