Hi all,

As I mentioned on yesterday’s forum, I made a patch to fix the gitattributes issues in the tools repo.

And the last call of review for the main repo normalization:

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283

Plan to have them both merged on next Tuesday.

Best Regards,

Kevin

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M
Sent: Tuesday, February 9, 2021 10:03 AM
To: tf-m@lists.trustedfirmware.org; Anton Komlev <Anton.Komlev@arm.com>
Cc: nd <nd@arm.com>
Subject: Re: [TF-M] TF-M git repo normalization

Hi,

I’d like to give a brief introduction on the git normalization before merging this patch.

@Anton Komlev, can I reserve 15-20 minutes of the next tech forum?

Best Regards,

Kevin

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M
Sent: Monday, February 8, 2021 10:56 AM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: Re: [TF-M] TF-M git repo normalization

Hi all,

Would like to merge the below patch *tomorrow* if there were no objections.

Best Regards,

Kevin

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M
Sent: Friday, February 5, 2021 10:37 AM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: Re: [TF-M] TF-M git repo normalization

This patch was generated by git command automatically:

$ git add --renormalize .

It does change any contents of the files, except the line-endings in the repository.

Your existing local working tree should not be affected when you pick up it or later when it’s merged.

The only file maintained manually is the  .gitattributes

Best Regards,

Kevin

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M
Sent: Friday, February 5, 2021 9:53 AM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] TF-M git repo normalization

Hi all,

Following the git normalization topic of the tech forum yesterday, I checked TF-M.

It has not been enabled the git normalization feature.

I’ve made a patch to make this happen.

Please check out or rebase your work upon this patch to see any issues.

Your existing working tree should not be affected regarding the line-endings.

What is the normalization?

To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other.

Reference: https://git-scm.com/docs/gitattributes

Best Regards,

Kevin