Said this, one may use his favorite line endings locally. When applying a
patch with different line endings, the applier of tge patch will either
reject the patch or fix line endings on thy fly.

Sorry for the various mails on the same thread. Sending from mobiles is not
really comfortable.

On 16 Oct 2016 5:13 p.m., "Dominik Psenner" <dpsen...@gmail.com> wrote:

> I suggest to agree on one line ending and use that throughout the
> repository.
>
> Until today the only rule that exists is that each file must use exactly
> one type of line endings. Mixed line endings are forbidden by svn
> properties.
>
> On 16 Oct 2016 4:21 p.m., "JJoe2" <g...@git.apache.org> wrote:
>
>> Github user JJoe2 commented on the issue:
>>
>>     https://github.com/apache/log4net/pull/25
>>
>>     The .gitattributes file you committed doesn’t specify line endings
>> for most file types including .cs and .csproj (the most commonly modified
>> ones).
>>
>>     However I don’t feel competent to say whether it’s really a good
>> idea.   Having read the section on “Refreshing the repository after
>> changing line endings”, it seems that a number of arcane git incantations
>> may be required to get everything working again after doing so.   Which
>> might cause problems for people who have forked but are struggling with git.
>>
>>
>>
>> ---
>> If your project is set up for it, you can reply to this email and have
>> your
>> reply appear on GitHub as well. If your project does not have this feature
>> enabled and wishes so, or if the feature is enabled but not working,
>> please
>> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
>> with INFRA.
>> ---
>>
>

Reply via email to