From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Joey Hess <joey@kitenet.net>
Subject: [PATCH v2 10/10] Documentation/git-replace: describe --format option
Date: Sat, 07 Dec 2013 17:21:05 +0100 [thread overview]
Message-ID: <20131207162106.21478.34711.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20131207160514.21478.72966.chriscool@tuxfamily.org>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
Documentation/git-replace.txt | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-replace.txt b/Documentation/git-replace.txt
index f373ab4..7a07828 100644
--- a/Documentation/git-replace.txt
+++ b/Documentation/git-replace.txt
@@ -10,7 +10,7 @@ SYNOPSIS
[verse]
'git replace' [-f] <object> <replacement>
'git replace' -d <object>...
-'git replace' -l [<pattern>]
+'git replace' [--format=<format>] [-l [<pattern>]]
DESCRIPTION
-----------
@@ -70,6 +70,23 @@ OPTIONS
Typing "git replace" without arguments, also lists all replace
refs.
+--format=<format>::
+ When listing, use the specified <format>, which can be one of
+ 'short', 'medium' and 'full'. When omitted, the format
+ defaults to 'short'.
+
+FORMATS
+-------
+
+The following format are available:
+
+* 'short':
+ <replaced sha1>
+* 'medium':
+ <replaced sha1> -> <replacement sha1>
+* 'full'
+ <replaced sha1> (<replaced type>) -> <replacement sha1> (<replacement type>)
+
CREATING REPLACEMENT OBJECTS
----------------------------
--
1.8.5.1.102.g090758b
prev parent reply other threads:[~2013-12-07 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 16:20 [PATCH v2 00/10] teach replace objects to sha1_object_info_extended() Christian Couder
2013-12-07 16:20 ` [PATCH v2 01/10] Rename READ_SHA1_FILE_REPLACE flag to LOOKUP_REPLACE_OBJECT Christian Couder
2013-12-07 16:20 ` [PATCH v2 02/10] replace_object: don't check read_replace_refs twice Christian Couder
2013-12-07 16:20 ` [PATCH v2 03/10] Introduce lookup_replace_object_extended() to pass flags Christian Couder
2013-12-07 16:20 ` [PATCH v2 04/10] Add an "unsigned flags" parameter to sha1_object_info_extended() Christian Couder
2013-12-07 16:21 ` [PATCH v2 05/10] t6050: show that git cat-file --batch fails with replace objects Christian Couder
2013-12-07 16:21 ` [PATCH v2 06/10] sha1_file: perform object replacement in sha1_object_info_extended() Christian Couder
2013-12-07 16:21 ` [PATCH v2 07/10] builtin/replace: teach listing using short, medium or full formats Christian Couder
2013-12-07 16:21 ` [PATCH v2 08/10] t6050: add tests for listing with --format Christian Couder
2013-12-09 3:19 ` Eric Sunshine
2013-12-09 5:58 ` Christian Couder
2013-12-07 16:21 ` [PATCH v2 09/10] builtin/replace: unset read_replace_refs Christian Couder
2013-12-07 19:02 ` Jakub Narebski
2013-12-07 19:37 ` Christian Couder
2013-12-07 16:21 ` Christian Couder [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131207162106.21478.34711.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
--cc=peff@peff.net \
/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).