[wildfly-dev] Github repo line endings unification advice

[Lukas Kubik]

Hi Jason,

Thanks for the explanation. Is there any reason why you don't use "* text=auto" option?


Lukas

----- Original Message -----
From: "Jason T. Greene" <jason.greene at redhat.com>
To: "Lukas Kubik" <lkubik at redhat.com>
Cc: wildfly-dev at lists.jboss.org
Sent: Wednesday, June 10, 2015 2:04:53 PM
Subject: Re: [wildfly-dev] Github repo line endings unification advice

It's a mistake that the jsp files aren't in gitatttibutes. The reason that it hasn't gotten CRLF is probably a bit of luck, and a bit of the fact that most code editors try to preserve them on their own even on windows.

> On Jun 10, 2015, at 6:41 AM, Lukas Kubik <lkubik at redhat.com> wrote:
> 
> Hi,
> 
> I'm sorry that this is a little bit off-topic question but I already asked in the forum and nobody answered me. How do you guys deal with the line endings unification in your github repo? I saw that you don't have for example .jsp files in the .gitattributes file however all .jsp files in the WF repo uses LF ending. How do you check that windows CRLF won't get merged with some PR?
> 
> We are currently discussing the unification of the line endings in the Keycloak repo so I would like to kindly ask you for any advice.
> 
> 
> Thank you for the answer.
> Regards,
> 
> Lukas
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev