TortoiseGit LFS pointer file display without native LFS client installed

Unresolved LFS Support Behavior in TortoiseGit

TortoiseGit delegates all network and LFS operations to the underlying Git for Windows installation. When Git LFS is not installed, LFS-tracked files appear as pointer files in the repository, but TortoiseGit's log viewer, diff dialog, and commit interface do not provide native warnings or indicators about missing LFS support.

The current behavior leaves users uncertain whether pointer files represent actual content or missing large files, especially when examining history or comparing changes across branches. This ambiguity increases when collaborating with team members who have LFS properly configured.

Key constraints include: Git for Windows version compatibility, absence of built-in LFS client in TortoiseGit, and reliance on external Git LFS installation for proper file handling. The tool's documentation does not clearly specify minimum LFS client requirements or expected behavior when LFS is unavailable.

Questions:

• Will TortoiseGit implement native UI warnings when LFS-tracked files are encountered without a configured Git LFS client?
• Should TortoiseGit detect and report LFS pointer file status differently than regular text content in its diff and log viewers?
• Is there a documented threshold for file size or pointer format that triggers special handling in TortoiseGit's file display components?