Lars Schneider writes:
>> Also the exact format of these attributes entries looks like very
>> closely tied to GitHub LFS and not generic (for example, there is no
>> reason to expect that any large-file support would always use the
>> "filter" mechanism or the gitattributes mechanism for that
>>
On 09 Sep 2015, at 19:20, Junio C Hamano wrote:
> larsxschnei...@gmail.com writes:
>
>> @@ -2226,17 +2355,16 @@ class P4Sync(Command, P4UserMap):
>> text = regexp.sub(r'$\1$', text)
>> contents = [ text ]
>>
>> -self.gitStream.write("M %s inline %s\n" % (git_mod
larsxschnei...@gmail.com writes:
> @@ -2226,17 +2355,16 @@ class P4Sync(Command, P4UserMap):
> text = regexp.sub(r'$\1$', text)
> contents = [ text ]
>
> -self.gitStream.write("M %s inline %s\n" % (git_mode, relPath))
> +if relPath == '.gitattributes':
>
From: Lars Schneider
Perforce repositories can contain large (binary) files. Migrating these
repositories to Git generates very large local clones. External storage
systems such as Git LFS [1], Git Fat [2], or Git Media [2] try to
address this problem.
Add a generic mechanism to detect large fil
4 matches
Mail list logo