I added the .gitattributes file to core, tools, and actinium and applied the line endings conversion documented on the
GitHub help site below.
I would say, this should be done to Scandium only when all fixes and features for the release are done.
What is you status there?
Ciao
Matthias
From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kai
Sent: Freitag, 28. August 2015 16:46
To: Californium (Cf) developer discussions <cf-dev@xxxxxxxxxxx>
Subject: Re: [cf-dev] Line endings
I have configured versions 1.0.0 and 1.1.0 for the Californium project in Bugzilla so that we can schedule the open issues for these versions, thus providing an overview of which issues should be fixed in 1.0.0 and which ones will be fixed
later ...
Great, this sounds like an informed decision then! :)
I suggest we finish all fixes for 1.0.0 and then do a "prettifying" commit changing the line endings. Maybe there are some such changes like updating the copyright date in all files...
> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Hudalla Kai (INST/ESY)
> Sent: Freitag, 28. August 2015 14:00
> To: Californium (Cf) developer discussions <cf-dev@xxxxxxxxxxx>
> Subject: Re: [cf-dev] Line endings
>
> From what I learned from several Stack Overflow posts, I think that it makes
> most sense to have Unix line endings (\n) in the repository (GitHub).
> This way, people developing on Linux etc can simply keep the files as-is and
> people working on Windows can have Git translate between LF <-> CRLF
> during check-out/-in automatically.
> This can be done on Windows by setting the Git configuration property
> core.autcrlf = true at either the global or repository level.
>
> On GitHub I also found a page
https://help.github.com/articles/dealing-with-
> line-endings/ providing some advice on how to "normalize" all line endings in
> a repo in one step.
>
> Regards,
> Kai
>
> ________________________________________
> Von: cf-dev-bounces@xxxxxxxxxxx [cf-dev-bounces@xxxxxxxxxxx]" im
> Auftrag von "Kovatsch Matthias [kovatsch@xxxxxxxxxxx]
> Gesendet: Mittwoch, 5. August 2015 13:57
> An: Californium (Cf) developer discussions
> Betreff: [cf-dev] Line endings
>
> Hi all
>
> With more committers on board, the issue of different line endings popped
> up again. I also found a few files that were inconsistent.
>
> Originally, the code started out with Windows line endings. I consider this the
> "safer" why because I never encountered an editor that cannot handle \r\n
> (but the other way round).
>
> However, if the overall default for open source is \n, then we can change to
> this and avoid the confusion in commits and pull-requests. Please share your
> experience or knowledge on that, so we can put this to an educated vote.
>
> Ciao
> Matthias
>
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
|
