Re: [git-users] Re: Error on repository clone: select: Not enough memory ... index-pack failed
On Fri, Jun 12, 2015 at 12:35:49PM -0700, Dheeraj Verma wrote: > Same problem here That's an almost 3 year old email you've dug out there! Was there a solution posted back then? If not, what have you checked and tried yourself? /M > On Wednesday, July 11, 2012 at 12:58:19 PM UTC+5:30, Sergiu wrote: > > > > Hi. > > > > I've been struggling for few days now with this, so I was hoping I could > > get some suggestions here. > > It's about cloning a repo. It used to work, but it just started to throw > > this error when I "git clone ssh://git@hostname:10101/test.git": > > > > remote: Counting objects: 11401, done. > > remote: Compressing objects: 100% (9278/9278), done. > > select: Not enough memory4561/11401), 206.60 MiB | 1.01 MiB/s > > fatal: The remote end hung up unexpectedly > > fatal: early EOF > > fatal: index-pack failed > > > > I cannot clone this repo anymore. It always dies around 206-208 MiB. > > Anyone dealt with this before? Any suggestions? Thank you. > > > > # Server: CentOS release 6.2 (Final) 2.6.32-220.el6.x86_64 > > # cat /proc/meminfo > > # MemTotal: 16316936 kB (16 316 936 kilobytes = 15.5610428 gigabytes) > > # MemFree: 5251088 kB (5 251 088 kilobytes = 5.00782776 gigabytes) > > > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus The day after tomorrow is the third day of the rest of your life. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
[git-users] Re: Error on repository clone: select: Not enough memory ... index-pack failed
Same problem here On Wednesday, July 11, 2012 at 12:58:19 PM UTC+5:30, Sergiu wrote: > > Hi. > > I've been struggling for few days now with this, so I was hoping I could > get some suggestions here. > It's about cloning a repo. It used to work, but it just started to throw > this error when I "git clone ssh://git@hostname:10101/test.git": > > remote: Counting objects: 11401, done. > remote: Compressing objects: 100% (9278/9278), done. > select: Not enough memory4561/11401), 206.60 MiB | 1.01 MiB/s > fatal: The remote end hung up unexpectedly > fatal: early EOF > fatal: index-pack failed > > I cannot clone this repo anymore. It always dies around 206-208 MiB. > Anyone dealt with this before? Any suggestions? Thank you. > > # Server: CentOS release 6.2 (Final) 2.6.32-220.el6.x86_64 > # cat /proc/meminfo > # MemTotal: 16316936 kB (16 316 936 kilobytes = 15.5610428 gigabytes) > # MemFree: 5251088 kB (5 251 088 kilobytes = 5.00782776 gigabytes) > > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Can not undo multiple git rebase using git reflog & git reset --hard
Thanks Rémi, you saved me a lot time. I thought, if I do "git reflog" and it displays all changes I did, it will roll back through all changes & branches. After your answer everything become clear. However, I think the best implementation would be to work like I proposed to work. Thanks very much! Konrad 2015. június 10., szerda 17:04:44 UTC+2 időpontban Rémi Rampin a következőt írta: > > 2015-06-09 15:55 GMT-04:00 Konrád Lőrinczi >: > >> I did a few git rebase interactive between branches, but when I use git >> reflog & git reset --hard HEAD@{N} I can not get the same branch hierarchy >> as it was before. >> git reflog >> git reset --hard HEAD@{14} >> > > Hi, > > You seem to be confused as to what git reset --hard does -- it doesn't > reset your whole repository, it moves a single branch head to a different > commit. > > You will have to consult the reflog of each branch (git reflog local_dev), > and reset that branch to the correct point (git checkout local_dev; git > reset --hard local_dev@{N}). > > Good luck > -- > Rémi Rampin > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.