On Feb 20, 2022 at 3:29:31 AM, Barak A. Pearlmutter
wrote:
> I will file an issue upstream. But I don't expect them to care,
> because github (the company) probably views this issue as a feature,
> not a bug. This issue ties people to a single central repository and
> makes migration nearly
I will file an issue upstream. But I don't expect them to care,
because github (the company) probably views this issue as a feature,
not a bug. This issue ties people to a single central repository and
makes migration nearly impossible, at least for non-wizards. Which is
basically their business
Thanks for reporting this. I agree that it sounds useful, though it might
be very challenging due to the decentralized nature of git-lfs. I’m happy
to keep this bug open, but it seems better served for the upstream tracker
at https://github.com/git-lfs/git-lfs/issues.
Stephen
On Jan 31, 2022 at
Package: git-lfs
Version: 3.0.2-1
Severity: wishlist
X-Debbugs-Cc: none, Barak A. Pearlmutter
I have a repo whose only remote is on a gitlab instance. I'm using
git-lfs to manage large binary files in this repo. The remote goes down.
Now "git add foo.pdf / git commit", when *.pdf files are
4 matches
Mail list logo
