From: tim.nordell at logicpd.com (Tim Nordell)
Subject: [PATCH 0/2] ui-log: Don't print out unknown decoration types
Date: Fri, 26 Feb 2016 14:57:29 -0600 [thread overview]
Message-ID: <1456520251-22349-1-git-send-email-tim.nordell@logicpd.com> (raw)
On our server we have some ref spaces that shouldn't be displayed in
the main log. The command line tool "git log" does not display these
either. Add some additional smarts to ui-log so that it uses the
enumeration types returned by the internals of git to determine
whether or not to display a tag, as well as converting the logic
in the log to use these enumerations rather than reinventing the
wheel for these.
Tim Nordell (2):
ui-log: Do not always emit decoration span
ui-log: Simplify decoration code
ui-log.c | 58 +++++++++++++++++++++++++++++-----------------------------
1 file changed, 29 insertions(+), 29 deletions(-)
--
2.4.9
next reply other threads:[~2016-02-26 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 20:57 tim.nordell [this message]
2016-02-26 20:57 ` [PATCH 1/2] ui-log: Do not always emit decoration span tim.nordell
2016-02-28 12:40 ` john
2016-05-12 15:16 ` Jason
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=1456520251-22349-1-git-send-email-tim.nordell@logicpd.com \
--to=cgit@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).