git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Magnus Bäck" <baeck@google.com>
To: Thomas Manson <dev.mansonthomas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Selectively commit/publish files to GIT
Date: Fri, 8 Nov 2013 09:13:30 -0500	[thread overview]
Message-ID: <20131108141329.GA26790@google.com> (raw)
In-Reply-To: <CA+PenvEDY6mc+DyjXy4ebZKdK4R=ucM28MDXGC42XKxvJ=a-pQ@mail.gmail.com>

On Friday, November 08, 2013 at 05:52 EST,
     Thomas Manson <dev.mansonthomas@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 --
> --all
> 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-3.0.0.110.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
baeck@google.com

  reply	other threads:[~2013-11-08 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 10:52 Selectively commit/publish files to GIT Thomas Manson
2013-11-08 14:13 ` Magnus Bäck [this message]
2013-11-08 22:51   ` Thomas Manson
2013-11-08 23:01     ` Thomas Manson
2013-11-08 23:50 ` Keshav Kini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131108141329.GA26790@google.com \
    --to=baeck@google.com \
    --cc=dev.mansonthomas@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).