From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: GIT_TRACE_PACKET is not documented
Date: Sat, 4 Jun 2011 16:17:27 +0200 [thread overview]
Message-ID: <201106041617.27944.jnareb@gmail.com> (raw)
While GIT_TRACE is documented on git manpage, and mentioned in RelNotes,
GIT_MERGE_VERBOSITY is documented on git manpage and mentioned on
git-merge manpage and other... GIT_TRACE_PACKET isn't documented
_anywhere_:
$ git grep GIT_TRACE_PACKET
pkt-line.c:static const char trace_key[] = "GIT_TRACE_PACKET";
--
Jakub Narebski
Poland
next reply other threads:[~2011-06-04 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 14:17 Jakub Narebski [this message]
2011-06-06 16:13 ` GIT_TRACE_PACKET is not documented Jeff King
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=201106041617.27944.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.