From: Junio C Hamano <gitster@pobox.com>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: git@vger.kernel.org, eyvind.bernhardsen@gmail.com, tboegi@web.de,
sandals@crustytoothpaste.net
Subject: Re: [PATCH v4 1/1] docs: rewrite the documentation of the text and eol attributes
Date: Wed, 03 May 2023 09:06:56 -0700 [thread overview]
Message-ID: <xmqq8re5wg9r.fsf@gitster.g> (raw)
In-Reply-To: <20230503044656.221175-2-alexhenrie24@gmail.com> (Alex Henrie's message of "Tue, 2 May 2023 22:46:56 -0600")
Alex Henrie <alexhenrie24@gmail.com> writes:
> These two sentences are confusing because the description of the text
> attribute sounds exactly the same as the description of the text=auto
> attribute:
> ...
> Rephrase the documentation of text, text=auto, eol, eol=crlf, and eol=lf
> to be clear about how they are the same, how they are different, and in
> what cases conversion is performed.
>
> Helped-by: Torsten Bögershausen <tboegi@web.de>
> Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
> ---
> Documentation/gitattributes.txt | 59 +++++++++++++++++----------------
> 1 file changed, 31 insertions(+), 28 deletions(-)
Will replace. Unless I hear objections soon, I'll mark it for
'next' and merge it down. Thanks.
next prev parent reply other threads:[~2023-05-03 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 2:35 [PATCH v3 0/1] docs: rewrite the documentation of the text and eol attributes Alex Henrie
2023-05-01 2:35 ` [PATCH v3 1/1] " Alex Henrie
2023-05-02 4:17 ` Torsten Bögershausen
2023-05-02 5:59 ` Alex Henrie
2023-05-02 16:27 ` Felipe Contreras
2023-05-03 4:46 ` [PATCH v4 0/1] " Alex Henrie
2023-05-03 4:46 ` [PATCH v4 1/1] " Alex Henrie
2023-05-03 16:06 ` Junio C Hamano [this message]
2023-05-03 19:00 ` Torsten Bögershausen
2023-05-03 19:27 ` Junio C Hamano
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=xmqq8re5wg9r.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=alexhenrie24@gmail.com \
--cc=eyvind.bernhardsen@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=tboegi@web.de \
/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).