From: "Yagnatinsky, Mark" <mark.yagnatinsky@bofa.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Torsten Bögershausen'" <tboegi@web.de>,
"'git@vger.kernel.org'" <git@vger.kernel.org>
Subject: RE: suggestion for improved docs on autocrlf
Date: Mon, 12 Aug 2019 18:30:08 +0000 [thread overview]
Message-ID: <e47edd8a079d40c8a4151d4d73060b31@bofa.com> (raw)
In-Reply-To: <xmqqo90u9ric.fsf@gitster-ct.c.googlers.com>
Okay, let me be more explicit :)
Suppose "git check-attr -a ." produces no output.
Now, is predictable?
-----Original Message-----
From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On Behalf Of Junio C Hamano
Sent: Monday, August 12, 2019 2:19 PM
To: Yagnatinsky, Mark <mark.yagnatinsky@bofa.com>
Cc: 'Torsten Bögershausen' <tboegi@web.de>; 'git@vger.kernel.org' <git@vger.kernel.org>
Subject: Re: suggestion for improved docs on autocrlf
"Yagnatinsky, Mark" <mark.yagnatinsky@bofa.com> writes:
> ... Assuming the repo has no .gitattributes,
> is it possible to predict what line endings sample.txt will end up with in my repo?
> Or does it depend on more information than what I've just written?
Binary packagers can ship custom attributes and config that applies
globally to the installation, which may affect operations in all of
your repositories, can't they?
----------------------------------------------------------------------
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.
next prev parent reply other threads:[~2019-08-12 18:30 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 [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e47edd8a079d40c8a4151d4d73060b31@bofa.com \
--to=mark.yagnatinsky@bofa.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).