From: Michele Ballabio <barra_cuda@katamail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH v2] Document ls-files -t as semi-obsolete.
Date: Tue, 27 Jul 2010 21:07:49 +0200 [thread overview]
Message-ID: <201007272107.50204.barra_cuda@katamail.com> (raw)
In-Reply-To: <1280162391-18701-1-git-send-email-Matthieu.Moy@imag.fr>
On Monday 26 July 2010, Matthieu Moy wrote:
> Documentation/git-ls-files.txt | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt
> index 3521637..2cc3243 100644
> --- a/Documentation/git-ls-files.txt
> +++ b/Documentation/git-ls-files.txt
> @@ -106,6 +106,12 @@ OPTIONS
> with `-s` or `-u` options does not make any sense.
>
> -t::
> + This feature is semi-deprecated. For scripting purpose,
> + linkgit:git-status[1] `--porcelain` is almost always a
> + superior alternative, and users should look at
> + linkgit:git-status[1] `--short` or linkgit:git-diff[1]
> + `--name-status` for more user-friendly alternatives.
> +
> Identify the file status with the following tags (followed by
> a space) at the start of each line:
> H:: cached
I think this breaks formatting. Shouldn't it be more like the following?
(I.e. with a single '+' before "Identify...").
And maybe rephrase the line
"Identify the file status with the following tags (followed by
a space) at the start of each line"
into
"This option identifies..."
just to set apart "semi-deprecation" and "explanation" of the option.
diff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt
index 3521637..ef84d41 100644
--- a/Documentation/git-ls-files.txt
+++ b/Documentation/git-ls-files.txt
@@ -106,15 +106,21 @@ OPTIONS
with `-s` or `-u` options does not make any sense.
-t::
- Identify the file status with the following tags (followed by
- a space) at the start of each line:
- H:: cached
- S:: skip-worktree
- M:: unmerged
- R:: removed/deleted
- C:: modified/changed
- K:: to be killed
- ?:: other
+ This feature is semi-deprecated. For scripting purpose,
+ linkgit:git-status[1] `--porcelain` is almost always a
+ superior alternative, and users should look at
+ linkgit:git-status[1] `--short` or linkgit:git-diff[1]
+ `--name-status` for more user-friendly alternatives.
++
+Identify the file status with the following tags (followed by
+a space) at the start of each line:
+H:: cached
+S:: skip-worktree
+M:: unmerged
+R:: removed/deleted
+C:: modified/changed
+K:: to be killed
+?:: other
-v::
Similar to `-t`, but use lowercase letters for files
next prev parent reply other threads:[~2010-07-27 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 16:39 [PATCH v2] Document ls-files -t as semi-obsolete Matthieu Moy
2010-07-27 17:36 ` Junio C Hamano
2010-07-27 19:07 ` Michele Ballabio [this message]
2010-07-27 21:02 ` Matthieu Moy
2010-07-27 21:11 ` [PATCH v3] " Matthieu Moy
2010-07-28 4:00 ` Jeff King
2010-07-28 7:24 ` [PATCH v4] " Matthieu Moy
2010-07-27 19:58 ` [PATCH v2] " Jeff King
2010-07-27 20:11 ` Matthieu Moy
2010-07-27 21:06 ` Jeff King
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=201007272107.50204.barra_cuda@katamail.com \
--to=barra_cuda@katamail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).