From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: "Yagnatinsky\, Mark" <mark.yagnatinsky@bofa.com>,
"'git\@vger.kernel.org'" <git@vger.kernel.org>
Subject: Re: suggestion for improved docs on autocrlf
Date: Tue, 13 Aug 2019 09:40:34 -0700 [thread overview]
Message-ID: <xmqq8srx9fy5.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190813154033.uhi7w5jgwcj4xan7@tb-raspi4> ("Torsten =?utf-8?Q?B=C3=B6gershausen=22's?= message of "Tue, 13 Aug 2019 17:40:33 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
>> Sigh. Okay, great, life makes sense again. I want to yell at my
>> IDE now.
>>
>> I now feel brave enough to attempt to come up with better wording
>> for autocrlf docs, if you think that's worth trying.
>
> That would be good, I am happy to review patches.
Good. Thanks for a good discussion.
prev parent reply other threads:[~2019-08-13 16:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 13:08 suggestion for improved docs on autocrlf Yagnatinsky, Mark
2019-08-08 20:56 ` Torsten Bögershausen
2019-08-08 21:19 ` Yagnatinsky, Mark
2019-08-08 23:08 ` Yagnatinsky, Mark
2019-08-09 3:34 ` Torsten Bögershausen
2019-08-09 15:34 ` Yagnatinsky, Mark
2019-08-11 12:10 ` Torsten Bögershausen
2019-08-12 13:47 ` Yagnatinsky, Mark
2019-08-12 15:46 ` Junio C Hamano
2019-08-12 15:52 ` Yagnatinsky, Mark
2019-08-12 17:10 ` Torsten Bögershausen
2019-08-12 18:00 ` Yagnatinsky, Mark
2019-08-12 18:18 ` Junio C Hamano
2019-08-12 18:30 ` Yagnatinsky, Mark
2019-08-13 3:24 ` Torsten Bögershausen
2019-08-13 15:31 ` Yagnatinsky, Mark
2019-08-13 15:40 ` Torsten Bögershausen
2019-08-13 15:44 ` Yagnatinsky, Mark
2019-08-14 16:28 ` Yagnatinsky, Mark
2019-08-15 4:56 ` Yagnatinsky, Mark
2019-08-16 4:20 ` Torsten Bögershausen
2019-08-16 19:12 ` Yagnatinsky, Mark
2019-08-13 16:40 ` Junio C Hamano [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=xmqq8srx9fy5.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mark.yagnatinsky@bofa.com \
--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).