From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
"Adam Roben" <aroben@apple.com>,
"Bryan Larsen" <bryan.larsen@gmail.com>,
"Matthias Urlichs" <smurf@smurf.noris.de>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH 0/3] hash-object doc: small fixes
Date: Mon, 20 May 2019 23:53:09 +0200 [thread overview]
Message-ID: <20190520215312.10363-1-avarab@gmail.com> (raw)
Small doc fixes. Maybe trivial enough to land in 2.22, but there's no
rush.
A pair of #leftoverbits I noticed is that we've implemented the
"--stdin-paths" option via unquote_c_style() from day one, so our
current docs lie (and still do with this series) about wanting
\n-delimited files, you can't hash a file called '"foo"' as you'd
expect, you need to pass '"\"foo\""'.
I wonder if we should document this at this point, or just change it
and add a "-z" option. None of our tests fail if I remove this
unquote_c_style() codepath, and it's never been documented, but
someone in the wild may have organically depended on it.
Ævar Arnfjörð Bjarmason (3):
hash-object doc: stop mentioning git-cvsimport
hash-object doc: elaborate on -w and --literally promises
hash-object doc: point to ls-files and rev-parse
Documentation/git-hash-object.txt | 22 +++++++++++++++++-----
1 file changed, 17 insertions(+), 5 deletions(-)
--
2.21.0.1020.gf2820cf01a
next reply other threads:[~2019-05-20 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 21:53 Ævar Arnfjörð Bjarmason [this message]
2019-05-20 21:53 ` [PATCH 1/3] hash-object doc: stop mentioning git-cvsimport Ævar Arnfjörð Bjarmason
2019-05-22 4:57 ` Jeff King
2019-05-20 21:53 ` [PATCH 2/3] hash-object doc: elaborate on -w and --literally promises Ævar Arnfjörð Bjarmason
2019-05-22 5:08 ` Jeff King
2019-05-24 10:04 ` Jakub Narebski
2019-05-24 10:12 ` Ævar Arnfjörð Bjarmason
2019-05-28 6:06 ` Jeff King
2019-05-28 16:56 ` Junio C Hamano
2019-05-28 16:49 ` Junio C Hamano
2019-05-20 21:53 ` [PATCH 3/3] hash-object doc: point to ls-files and rev-parse Ævar Arnfjörð Bjarmason
2019-05-22 5:15 ` 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=20190520215312.10363-1-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=aroben@apple.com \
--cc=bryan.larsen@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=smurf@smurf.noris.de \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.