threads / discuss / 18486

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

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

## tl;dr

One message between Mar 23, 2009 and Mar 23, 2009.

replies: 0people: 1as markdown or json

Toralf Förster· Mar 23, 2009, 10:37 UTC · lore

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