thanks for pointing that out. I must have overlooked the webpage,
when I saw that I thought it was some kind of alias that designated
files greater than a specific files (server side configurated as the
I'll try again ;)
On Fri, Nov 8, 2013 at 3:13 PM, Magnus Bäck <ba...@google.com> wrote:
> On Friday, November 08, 2013 at 05:52 EST,
> Thomas Manson <dev.mansontho...@gmail.com> wrote:
>> How can I search git history for big files and remove them, or mark
>> them to be not published ?
>> I've tryed this solution found on the link in the error:
>> git filter-branch --force --index-filter 'git rm --cached
>> --ignore-unmatch giant_file' --prune-empty --tag-name-filter cat --
>> git commit --amend -CHEAD
>> here is the error I have using the GitHub application on Mac :
>> (after that I intend to use Eclipse)
>> File Ressources/dwr/dwr-22.214.171.124.dev-src.zip is 67.69 MB; this is
>> larger than GitHub's recommended maximum file size of 50 MB
>> GH001: Large files detected.
>> Trace: 8f0259b29260f0c4d7ae4d4ae70e0306
>> See http://git.io/iEPt8g for more information.
>> File .bzr/repository/packs/a7bcd6ba235114ab88c80fe8a97adcfa.pack is
>> 178.76 MB; this exceeds GitHub's file size limit of 100 MB
> Did you actually replace the 'giant_file' placeholder with the path to
> *your* giant file? The error message indicates that you didn't, or that
> something else went wrong during the filtering.
> You can use 'git log' to look for commits touching particular pathnames,
> making it easy to verify that a file has been eradicated.
> git log --all -- path/to/big-honking-file.zip
> Magnus Bäck
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html