git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Robert Dailey <rcdailey.lists@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Hide decorations in git log
Date: Wed, 24 May 2017 10:39:48 -0400	[thread overview]
Message-ID: <20170524143948.orx2i26fobm7sd6n@sigill.intra.peff.net> (raw)
In-Reply-To: <CAHd499B+cyN=3XDqr7KgHSpyHLwi6bS=P_4beoS5fSkFhapAtw@mail.gmail.com>

On Wed, May 24, 2017 at 09:22:32AM -0500, Robert Dailey wrote:

> Is it possible to hide decorated refs in `git log` even if they are
> reachable from the refs I'm actually interested in seeing the logs of?

Sadly, no, there's no way to do this right now.

There was some discussion in this thread:

  http://public-inbox.org/git/20170119122630.27645-1-pclouds@gmail.com/T/#u

but no patches that do what you want.

Using the existing ref-selectors as discussed in that thread, it would
probably look something like:

  git log --oneline \
	--branches 'feature/*' --decorate-refs \
	--branches 'feature/*'

It sucks that you'd have to specify your refs twice (once to mark them
for decoration and once to use them as tips). But the flexibility would
let you do things like:

  git log --oneline \
	--branches 'feature/*' --decorate-refs \
	--tags --decorate-refs \
	HEAD

which decorates feature branches and tags, but only traverses from HEAD
(just as an example).

Anyway, none of that exists yet, so patches welcome.

-Peff

  parent reply	other threads:[~2017-05-24 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 14:22 Hide decorations in git log Robert Dailey
2017-05-24 14:31 ` Robert Dailey
2017-05-24 14:39 ` Jeff King [this message]
2017-05-26  8:48 ` Ævar Arnfjörð Bjarmason

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170524143948.orx2i26fobm7sd6n@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=rcdailey.lists@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).