git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Cliff Schomburg <clisc@microsoft.com>
To: "gitster@pobox.com" <gitster@pobox.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: "git log" does not display refs info when executed via C# Process class on Windows
Date: Fri, 9 Aug 2019 22:16:40 +0000
Message-ID: <BN8PR21MB11560DB6FA18D85672CFE8FEB7D60@BN8PR21MB1156.namprd21.prod.outlook.com> (raw)
In-Reply-To: <xmqqblwyc8l8.fsf@gitster-ct.c.googlers.com>

Thanks, I will try that as well.  Strange it works on command line but not STDOUT though.

-----Original Message-----
From: Junio C Hamano <gitster@pobox.com> 
Sent: Friday, August 9, 2019 5:50 PM
To: Cliff Schomburg <clisc@microsoft.com>
Cc: SZEDER Gábor <szeder.dev@gmail.com>; git@vger.kernel.org
Subject: Re: "git log" does not display refs info when executed via C# Process class on Windows

Cliff Schomburg <clisc@microsoft.com> writes:

> Strangely, when I run this command:
>
> Git log origin/master --pretty=oneline --decorate -1
>
> I get the format I want from STDOUT.  However, when I try to filter it to show only the tag refs:
>
> Git log origin/master --pretty=oneline --decorate 
> --decorate-refs=^tag* -1
>
> No refs are returned to standard output again.  Only on the command line.
>
> Does --decorate-refs not return to STDOUT?

If you are asking for tags, which does not begin with a caret "^", perhaps drop "^" from the pattern?

The pattern is supposed to be wildmatch pattern, so it is already left anchored, e.g. --decorate-refs=ag* won't find any tag.



      reply	other threads:[~2019-08-09 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 19:36 Cliff Schomburg
2019-08-09 19:50 ` SZEDER Gábor
2019-08-09 20:11   ` Cliff Schomburg
2019-08-09 21:34   ` Cliff Schomburg
2019-08-09 21:49     ` Junio C Hamano
2019-08-09 22:16       ` Cliff Schomburg [this message]

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=BN8PR21MB11560DB6FA18D85672CFE8FEB7D60@BN8PR21MB1156.namprd21.prod.outlook.com \
    --to=clisc@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@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

git@vger.kernel.org list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ https://public-inbox.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:

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

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git