|tagger||Mike Frysinger <email@example.com>||Mon Jun 03 21:33:38 2019 -0400|
|author||Francois Ferrand <firstname.lastname@example.org>||Fri May 24 09:35:20 2019 +0200|
|committer||Francois Ferrand <email@example.com>||Fri May 24 12:06:33 2019 +0000|
project: Set config option to skip lfs process filter During sync, repo runs `git read-tree --reset -u -v HEAD` which causes git-lfs's smudge filter to run, which fails because git-lfs does not work with bare repositories. This was fixed in I091ff37998131e2e6bbc59aa37ee352fe12d7fcd to automatically disable this smudge filter. However, later versions of Git (2.11.0) introduced a new filter protocol , to avoid spawning a new command for each filtered file. This was implemented in Git-LFS 1.5.0 . This patch fixes the issue by setting the git lfs process filter, in addition to the smudge filter. For any projects that have LFS objects, `git lfs pull` must still be executed manually afterwards.  https://github.com/git/git/commit/edcc85814c87ebd7f3b1b7d3979fac3dfb84d308  https://github.com/git-lfs/git-lfs/pull/1617 Bug: https://crbug.com/gerrit/10911 Change-Id: I277fc68fdefc91514a2412b3887e3be9106cab48
Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.