сб, 24 янв. 2026 г. в 11:50, William Lallemand <[email protected]>:
> Hello Ilia, > > No idea what you are trying to do, your commit message does not explain the > intention behind this change. > > The LF/CRLF problem is a common mistake from developers using windows, that > don't configure their editor correctly, because windows uses CRLF by > default. > it is not a problem. you can specify either * text=auto pr (for some files) *.c text=crlf and line ending will be handled as you;ve specified in .gitattributes no need to blame developers on windows for not configuring line endings. I sent a patch previously which accidentally changed line endings in *.http files. I agree that per RFC line ending is supposed to be CRLF, but Willy told "You don't see them, but it has added CRs at the end of each line above for no reason.", I do not argue with Willy :) we can set crlf if it appropriate (to prevent accident line ending convertion) > > It's not a problem about the .http files, even worse, because these files > contains HTTP headers, that do need CRLF to ends their lines. > > So you just need to configure your tools correctly to show these > characters. > > Regards, > > On Fri, Jan 23, 2026 at 11:23:02PM +0100, Ilia Shipitsin wrote: > > Subject: [PATCH] MINOR: tell git to use LF end of files for *.http files > > ML details: > https://www.mail-archive.com/[email protected]/msg46454.html > > --- > > .gitattributes | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/.gitattributes b/.gitattributes > > index 4b566452d..7c1e779c0 100644 > > --- a/.gitattributes > > +++ b/.gitattributes > > @@ -1,3 +1,5 @@ > > SUBVERS export-subst > > VERDATE export-subst > > *.[ch] diff=cpp > > + > > +*.http text eol=lf > > -- > > 2.46.0.windows.1 > > > > > > >
