wacky ideas
This commit is contained in:
		
					parent
					
						
							
								ee3885d152
							
						
					
				
			
			
				commit
				
					
						c634dae66b
					
				
			
		
					 1 changed files with 17 additions and 0 deletions
				
			
		| 
						 | 
					@ -80,3 +80,20 @@ Thanks for your great work! :) -- [[anarcat]]
 | 
				
			||||||
> --[[Joey]]
 | 
					> --[[Joey]]
 | 
				
			||||||
 | 
					
 | 
				
			||||||
> Started some initial work in the `git-lfs` branch. --[[Joey]]
 | 
					> Started some initial work in the `git-lfs` branch. --[[Joey]]
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					## related ideas
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					A couple ideas for possible things that could also be done with git-lfs
 | 
				
			||||||
 | 
					integration. Just to keep in mind while implementing the above.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					* git-annex could support git-lfs pointer files. This would let a lfs 
 | 
				
			||||||
 | 
					  repo be cloned and git-annex used to manage the files in it with the
 | 
				
			||||||
 | 
					  finer control it allows compared to git-lfs.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					* A lfs API endpoint could serve out of a git-annex repository.
 | 
				
			||||||
 | 
					  One neat thing this would allow is, when git-annex knows an url
 | 
				
			||||||
 | 
					  where an object is located (from the web special remote or another
 | 
				
			||||||
 | 
					  special remote that registers an url), it could direct the lfs
 | 
				
			||||||
 | 
					  client to that url when it requests to download the object.
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue