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

should "git describe" include info about not already committed patches ?

From
TFToralf Förster <toralf.foerster@gmx.de>
Date
Mar 23, 2009, 10:37 UTC
Message-ID
<200903231137.19103.toralf.foerster@gmx.de>

I'm wondering, if there's a option for "git describe" to point out the changes (as seen with git diff) which are made w/o a commit to a current trunk.

-- 
MfG/Sincerely

Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Message 1 of 1 in “should "git describe" include info about not already committed patches ?”
  1. Toralf FörsterMar 23, 2009

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.