On Fri, 2018-12-14 at 20:57 +0100, Laszlo Ersek wrote: > On 12/14/18 18:12, Supreeth Venkatesh wrote: > > On Fri, 2018-12-14 at 14:24 +0100, Laszlo Ersek wrote: > > > On 12/14/18 11:59, Leif Lindholm wrote: > > > > Hmm, this gets me thinking... > > > > > > > > We were discussing before about doing a line ending conversion > > > > in > > > > edk2, and let the git gools provide native line endings (as > > > > designed). > > > > > > > > Is this a good opportunity to run a pilot with edk2-test, where > > > > much > > > > less history will be lost? > > > > > > Well, history won't be lost, in the sense that people running > > > "git > > > blame" will need one more execution of "git blame" (to "look > > > past" > > > the > > > whitespace change commit), but yes, it will result in a minor > > > inconvenience. > > > > > > And, I think, converting the edk2-test repo would not be a bad > > > test > > > at all. > > > > > > > Thanks Leif/Laszlo. I volunteer to try the tool. However, I admit > > that > > I have not tried this before, any pointers/instructions on how to > > do > > this? > > I imagine you'd run a "find" command to locate all source/text files > (skip ".git"), then feed them to xargs / dos2unix. > > The trick is more in the git settings, once the internal > representation > has been converted to LF only. I'm thinking that "core.whitespace", > "am.keepcr" and "core.autocrlf" should be set the "right way". (= to > be > researched) Never mind. I think I misread the initial email. I was expecting some git tool magic or script :). I can come up with one. Thanks.
> > Thanks > Laszlo _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
