From: Greg KH <greg@kroah.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: git doesn't like big files when pushing
Date: Wed, 1 Mar 2006 15:27:19 -0800 [thread overview]
Message-ID: <20060301232719.GA22068@kroah.com> (raw)
In-Reply-To: <7v8xrtepje.fsf@assigned-by-dhcp.cox.net>
On Wed, Mar 01, 2006 at 03:03:17PM -0800, Junio C Hamano wrote:
> Greg KH <greg@kroah.com> writes:
>
> > On Wed, Mar 01, 2006 at 02:08:02PM -0800, Greg KH wrote:
> >> 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 ;-).
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 <junkio@cox.net>
> 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 <junkio@cox.net>
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
next prev parent reply other threads:[~2006-03-01 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 22:08 git doesn't like big files when pushing Greg KH
2006-03-01 22:08 ` Greg KH
2006-03-01 22:20 ` Greg KH
2006-03-01 23:03 ` Junio C Hamano
2006-03-01 23:27 ` Greg KH [this message]
2006-03-01 23:35 ` Greg KH
2006-03-02 0:34 ` Greg KH
2006-03-02 0:45 ` Martin Langhoff
2006-03-01 23:00 ` Linus Torvalds
2006-03-02 12:43 ` Simon Richter
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=20060301232719.GA22068@kroah.com \
--to=greg@kroah.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.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).