list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Cliff Schomburg <>
To: "SZEDER Gábor" <>
Cc: "" <>
Subject: RE: "git log" does not display refs info when executed via C# Process class on Windows
Date: Fri, 9 Aug 2019 21:34:06 +0000
Message-ID: <> (raw)
In-Reply-To: <>

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?


-----Original Message-----
From: SZEDER Gábor <> 
Sent: Friday, August 9, 2019 3:51 PM
To: Cliff Schomburg <>
Subject: Re: "git log" does not display refs info when executed via C# Process class on Windows

On Fri, Aug 09, 2019 at 07:36:19PM +0000, Cliff Schomburg wrote:
> I have an open Git for Windows issue here:
> f91ab2d7cd011db47%7C1%7C0%7C637009771013658738&amp;sdata=PKPdRI0mC65Lx
> 2J5etYnp0fyzsk%2BXSGzGBWa12BLKEE%3D&amp;reserved=0
> "git log" works as expected from the command prompt.  But when I execute it via C# Process class and read from Standard Output, the refs are missing.
> Is anyone familiar with this issue?  Any idea why the output to CMD and STDOUT would be different?

Decorations, like color and refs pointing to a commit, are for humans, and humans read the terminal.  If the command's output doesn't go to a terminal, then no such decorations are shown by default.

Try invoking 'git log --decorate'; or, better yet, use your custom '--format=', especially if you intend to parse the output, 

  parent reply	other threads:[~2019-08-09 21:34 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 [this message]
2019-08-09 21:49     ` Junio C Hamano
2019-08-09 22:16       ` Cliff Schomburg

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:

  List information:

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

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	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/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

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

AGPL code for this site: git clone