From: "Toralf Förster" <toralf.foerster@gmx.de>
To: git@vger.kernel.org
Subject: should "git describe" include info about not already committed patches ?
Date: Mon, 23 Mar 2009 11:37:18 +0100 [thread overview]
Message-ID: <200903231137.19103.toralf.foerster@gmx.de> (raw)
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
reply other threads:[~2009-03-23 10:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903231137.19103.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox