Re: git doesn't like big files when pushing

Greg KH [off-list ref] writes:

On Wed, Mar 01, 2006 at 02:08:02PM -0800, Greg KH wrote:

quoted

I have a mail archive stored with git, in mbox form, and I made some
changes to a few of the files and checked them back in.

...

Ouch.  Running out of memory while deltifying sounds really bad.

Oh, and I'm using:
	$ git --version
	git version 1.2.3.g8c2f

if that helps or not.

It doen't, since I do not have 8c2fXXXX commit ;-).

I suspect "git push --thin origin" might help, if you are on my
"master" branch:

        diff-tree a79a276... (from 2245be3...)
        Author: Junio C Hamano [off-list ref]
        Date:   Mon Feb 20 00:09:41 2006 -0800

            Add git-push --thin.

            Maybe we would want to make this default before it graduates to
            the master branch, but in the meantime to help testing things,
            this allows you to say "git push --thin destination".

            Signed-off-by: Junio C Hamano [off-list ref]

        :100755 100755 706db99... 73dcf06... M	git-push.sh

On Wed, Mar 01, 2006 at 03:03:17PM -0800, Junio C Hamano wrote:

Greg KH [off-list ref] writes:

quoted

On Wed, Mar 01, 2006 at 02:08:02PM -0800, Greg KH wrote:

quoted

I have a mail archive stored with git, in mbox form, and I made some
changes to a few of the files and checked them back in.

...

Ouch.  Running out of memory while deltifying sounds really bad.

quoted

Oh, and I'm using:
	$ git --version
	git version 1.2.3.g8c2f

if that helps or not.

It doen't, since I do not have 8c2fXXXX commit ;-).

Heh, that's a merge on my tree, sorry.  My tree only has one change to
the git-format-patch.sh script.

858cbfbabe4ede5f5eba32041eb7448319e53e2a is the most recent commit from
your tree.

I suspect "git push --thin origin" might help, if you are on my
"master" branch:

        diff-tree a79a276... (from 2245be3...)
        Author: Junio C Hamano [off-list ref]
        Date:   Mon Feb 20 00:09:41 2006 -0800

            Add git-push --thin.

            Maybe we would want to make this default before it graduates to
            the master branch, but in the meantime to help testing things,
            this allows you to say "git push --thin destination".

            Signed-off-by: Junio C Hamano [off-list ref]

Will try that.  I eventually gave up on the last push when it ran for 45
minutes at full cpu usage, and X got killed by the OOM killer in the
kernel for some reason...

thanks,

greg k-h

On Wed, Mar 01, 2006 at 03:27:19PM -0800, Greg KH wrote:

On Wed, Mar 01, 2006 at 03:03:17PM -0800, Junio C Hamano wrote:

quoted

I suspect "git push --thin origin" might help, if you are on my
"master" branch:

        diff-tree a79a276... (from 2245be3...)
        Author: Junio C Hamano [off-list ref]
        Date:   Mon Feb 20 00:09:41 2006 -0800

            Add git-push --thin.

            Maybe we would want to make this default before it graduates to
            the master branch, but in the meantime to help testing things,
            this allows you to say "git push --thin destination".

            Signed-off-by: Junio C Hamano [off-list ref]

Will try that.  I eventually gave up on the last push when it ran for 45
minutes at full cpu usage, and X got killed by the OOM killer in the
kernel for some reason...

Nice, this worked!

Now what's the odds that when I pull from the server to another box
these same objects, the server will have the same problem as git-push
did?

will go try that now...

thanks,

greg k-h

On Wed, Mar 01, 2006 at 03:35:06PM -0800, Greg KH wrote:

On Wed, Mar 01, 2006 at 03:27:19PM -0800, Greg KH wrote:

quoted

On Wed, Mar 01, 2006 at 03:03:17PM -0800, Junio C Hamano wrote:

quoted

I suspect "git push --thin origin" might help, if you are on my
"master" branch:

        diff-tree a79a276... (from 2245be3...)
        Author: Junio C Hamano [off-list ref]
        Date:   Mon Feb 20 00:09:41 2006 -0800

            Add git-push --thin.

            Maybe we would want to make this default before it graduates to
            the master branch, but in the meantime to help testing things,
            this allows you to say "git push --thin destination".

            Signed-off-by: Junio C Hamano [off-list ref]

Will try that.  I eventually gave up on the last push when it ran for 45
minutes at full cpu usage, and X got killed by the OOM killer in the
kernel for some reason...

Nice, this worked!

Now what's the odds that when I pull from the server to another box
these same objects, the server will have the same problem as git-push
did?

Ok, no problem there either.

thanks for the pointer to that option.

greg k-h

On 3/2/06, Greg KH [off-list ref] wrote:

Ok, no problem there either.

thanks for the pointer to that option.

Now that it has been tested twice, it's about time it becomes the default ;-)

cheers,


martin