Revision 79a77109d3d0d364910ff7fa8c605c554dc4c3e0 authored by René Scharfe on 27 October 2014, 18:23:05 UTC, committed by Junio C Hamano on 28 October 2014, 17:33:50 UTC
The config option color.grep.match can be used to specify the highlighting
color for matching strings.  Add the options matchContext and matchSelected
to allow different colors to be specified for matching strings in the
context vs. in selected lines.  This is similar to the ms and mc specifiers
in GNU grep's environment variable GREP_COLORS.

Tests are from Zoltan Klinger's earlier attempt to solve the same
issue in a different way.

Signed-off-by: Rene Scharfe <l.s.r@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent eeff891
Raw File
git-write-tree.txt
git-write-tree(1)
=================

NAME
----
git-write-tree - Create a tree object from the current index


SYNOPSIS
--------
[verse]
'git write-tree' [--missing-ok] [--prefix=<prefix>/]

DESCRIPTION
-----------
Creates a tree object using the current index. The name of the new
tree object is printed to standard output.

The index must be in a fully merged state.

Conceptually, 'git write-tree' sync()s the current index contents
into a set of tree files.
In order to have that match what is actually in your directory right
now, you need to have done a 'git update-index' phase before you did the
'git write-tree'.


OPTIONS
-------
--missing-ok::
	Normally 'git write-tree' ensures that the objects referenced by the
	directory exist in the object database.  This option disables this
	check.

--prefix=<prefix>/::
	Writes a tree object that represents a subdirectory
	`<prefix>`.  This can be used to write the tree object
	for a subproject that is in the named subdirectory.

GIT
---
Part of the linkgit:git[1] suite
back to top