Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Large file management recommendation #1

Closed
daviddwlee84 opened this issue Dec 5, 2018 · 3 comments
Closed

Large file management recommendation #1

daviddwlee84 opened this issue Dec 5, 2018 · 3 comments

Comments

@daviddwlee84
Copy link

I found that you said the MNIST dataset was exceeded the maximum storage of the Github limitation.
Maybe you can try to use git-lfs to manage that file then you won't need to keep the file in the different place!

@Dod-o
Copy link
Owner

Dod-o commented Dec 5, 2018

I found that you said the MNIST dataset was exceeded the maximum storage of the Github limitation.
Maybe you can try to use git-lfs to manage that file then you won't need to keep the file in the different place!

I actually tried,but when I clone it I only got 1kb of dataset.
I will try again, thank you.

@daviddwlee84
Copy link
Author

Maybe use git lfs pull to fetch lfs files. (reference)
And it said that

Git will only fetch LFS files that match patterns in your .gitattributes

Maybe another reason is that the file doesn't list in .gitattributes. Good luck :)

@Dod-o
Copy link
Owner

Dod-o commented Dec 8, 2018

I was going to try it today, but I suddenly felt that if the dataSet was too large, it maybe very inconvenient to clone.
So I think it's better to maintain the data size, don't you think?
Best wishes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants