From: Junio C Hamano <gitster@pobox.com>
To: D无数 <wushuripple@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: End-of-line comments are prompted with "is not a valid attribute name"
Date: Wed, 13 Dec 2023 11:22:53 -0800 [thread overview]
Message-ID: <xmqqsf45nbzm.fsf@gitster.g> (raw)
In-Reply-To: <CAOQ=bxz8txyOt6p5L0qfx5DFKfxUhWvHW0pJP+YTbWVfBpvYxg@mail.gmail.com> ("D无数"'s message of "Thu, 14 Dec 2023 01:32:11 +0800")
D无数 <wushuripple@gmail.com> writes:
> This is my .gitattributes:
> ```
> res/csv/*.txt eol=lf # 保证csv为lf,以匹配解析格式
I do not think of any version of Git ignoring what you wrote after #
(including #) in the middle of the line.
> # Custom for Visual Studio
I know I designed the parser to allow this as a comment, though.
So
> When performing certain operations:
> ···shell
>> git status
> # is not a valid attribute name: .gitattributes:1
This is totally expected; nothing to see here.
next prev parent reply other threads:[~2023-12-13 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 17:32 End-of-line comments are prompted with "is not a valid attribute name" D无数
2023-12-13 19:22 ` Junio C Hamano [this message]
2023-12-17 17:15 ` Junio C Hamano
2023-12-17 17:28 ` D无数
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=xmqqsf45nbzm.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=wushuripple@gmail.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).