git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Castro Alvarez, Sebastian" <s.castro.alvarez@rug.nl>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: could not fork child process rebasing required
Date: Thu, 12 Sep 2019 10:49:59 +0200	[thread overview]
Message-ID: <CAMr8YN7aa9yK3TSqVhQjn2DG7vU_zJs9SHvznPefay+Mxs_Qsg@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1909121044250.47@tvgsbejvaqbjf.bet>

Hi Johannes,

I have tried with both versions 32-bit and 64-bit, none of them work
for me, I still get the same error. :(

best,
Sebastian

On Thu, Sep 12, 2019 at 10:45 AM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> Hi Sebastian,
>
> On Wed, 11 Sep 2019, Castro Alvarez, Sebastian wrote:
>
> > I have recently updated my computer to W10. So, I reinstalled the
> > newest version of Git, and it is not working. It gives the following
> > error:
> >
> > Error: Could not fork child process: Resource temporarily unavailable (-1).
> > DLL rebasing may be required; see 'rebaseall / rebase --help'.
>
> This sounds as if you tried to install the 32-bit version of Git for
> Windows? If so, please install the 64-bit version instead.
>
> Ciao,
> Johannes



-- 
Sebastian Castro Alvarez
PhD student
Department of Psychometrics & Statistics
Heymans Institute for Psychological Research
University of Groningen
https://www.rug.nl/staff/s.castro.alvarez/

  reply	other threads:[~2019-09-12  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 13:00 could not fork child process rebasing required Castro Alvarez, Sebastian
2019-09-12  8:45 ` Johannes Schindelin
2019-09-12  8:49   ` Castro Alvarez, Sebastian [this message]
2019-09-12 11:28     ` Johannes Schindelin
2019-09-12 14:10       ` Castro Alvarez, Sebastian

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=CAMr8YN7aa9yK3TSqVhQjn2DG7vU_zJs9SHvznPefay+Mxs_Qsg@mail.gmail.com \
    --to=s.castro.alvarez@rug.nl \
    --cc=Johannes.Schindelin@gmx.de \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).