News for hackers. Stuff that matters.
Re:Converting a Git repo from tabs to spaces (2016) by IshKebab on Friday May 02, 2025 @10:37AM (#43870408)
It would be a lot more usable if you could put that info in the commit.
Re:Converting a Git repo from tabs to spaces (2016) by OptionOfT on Friday May 02, 2025 @10:44AM (#43870520)
That on its own is a security risk, as it would introduce means to hide a commit in the commit itself.

At least with the . file you have to make 2 separate transactions.

Re:Converting a Git repo from tabs to spaces (2016) by IshKebab on Friday May 02, 2025 @01:12PM (#43872428)
No it wouldn't. You would still be able to see the commit in logs and file histories and if you ran blame without the skipping option.
Re:Converting a Git repo from tabs to spaces (2016) by prepend on Friday May 02, 2025 @03:43PM (#43873913)
No. I don’t want the author to make that decision for me. I’d rather git record everything and then I can choose how to view or render it.

Different people have different view preferences.

Re:Converting a Git repo from tabs to spaces (2016) by jayd16 on Friday May 02, 2025 @10:16PM (#43876365)
Ok but why not both checked in and user settings with the user overriding the repo?
Re:Converting a Git repo from tabs to spaces (2016) by mbork_pl on Saturday May 03, 2025 @05:30AM (#43877887)
I would guess quit a few malware authors would also love such a feature.