update git large files article
This commit is contained in:
		
							parent
							
								
									655db813be
								
							
						
					
					
						commit
						8b9d58e08c
					
				
					 1 changed files with 14 additions and 1 deletions
				
			
		| 
						 | 
					@ -1,6 +1,7 @@
 | 
				
			||||||
---
 | 
					---
 | 
				
			||||||
title: Git and large files
 | 
					title: Git and large files
 | 
				
			||||||
date: 2021-12-29
 | 
					date: 2021-12-29
 | 
				
			||||||
 | 
					update: 2025-08-25
 | 
				
			||||||
---
 | 
					---
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Git is a cornerstone of software development nowadays, it has become the
 | 
					Git is a cornerstone of software development nowadays, it has become the
 | 
				
			||||||
| 
						 | 
					@ -97,7 +98,7 @@ Contrary to Git LFS, you can see what content is currently
 | 
				
			||||||
unwanted files](https://git-annex.branchable.com/tips/deleting_unwanted_files/).
 | 
					unwanted files](https://git-annex.branchable.com/tips/deleting_unwanted_files/).
 | 
				
			||||||
It is a more complex solution but it is more flexible.
 | 
					It is a more complex solution but it is more flexible.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
## What I recommend
 | 
					## What I recommend(ed) in 2021
 | 
				
			||||||
 | 
					
 | 
				
			||||||
I think git-annex gives the user more control over its data: it can be fully
 | 
					I think git-annex gives the user more control over its data: it can be fully
 | 
				
			||||||
decentralized and offers tools to manage its content.
 | 
					decentralized and offers tools to manage its content.
 | 
				
			||||||
| 
						 | 
					@ -105,6 +106,18 @@ decentralized and offers tools to manage its content.
 | 
				
			||||||
Git LFS is simpler and more widely used, but once you hit one of its limitation,
 | 
					Git LFS is simpler and more widely used, but once you hit one of its limitation,
 | 
				
			||||||
it can be costly to break free.
 | 
					it can be costly to break free.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					## What I recommend in 2025
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					As of 2025, I changed my mind and I think solution 1 is simpler and almost as
 | 
				
			||||||
 | 
					powerful as solution 3. You store all your data in git, manage clones with [partial support](https://git-scm.com/docs/partial-clone)
 | 
				
			||||||
 | 
					so you only fetch what is relevant, and you can prune assets by pruning your
 | 
				
			||||||
 | 
					repository like you would do with git-annex.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Support for offloading large files to external servers is on the roadmap with
 | 
				
			||||||
 | 
					[Large Object Promisor](https://git-scm.com/docs/large-object-promisors) if
 | 
				
			||||||
 | 
					your repository inflates too much.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
## Links
 | 
					## Links
 | 
				
			||||||
 | 
					
 | 
				
			||||||
- [Large files with Git: LFS and git-annex](https://lwn.net/Articles/774125/)
 | 
					- [Large files with Git: LFS and git-annex](https://lwn.net/Articles/774125/)
 | 
				
			||||||
 | 
					- [The future of large files in Git is Git](https://tylercipriani.com/blog/2025/08/15/git-lfs/)
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue