git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Pickens <jepicken@gmail.com>
To: Git ML <git@vger.kernel.org>
Subject: Background processes in post-receive hook
Date: Sat, 2 Apr 2011 16:03:43 -0700	[thread overview]
Message-ID: <AANLkTinrEt6DkwhknpDZ0iV9PR+7bBd3DAaPRJOgNFTG@mail.gmail.com> (raw)

Hi,

I have a post-receive hook (bash script) that launches several background
processes and exits immediately.  I do that so I don't have to wait for the
background processes to finish every time I push to the repository, but Git
seems to wait for them to finish anyways, even though the post-receive hook
itself already exited.  Is there any way to stop Git from waiting and let the
push finish immediately?  Sorry if I'm missing something obvious...

Thanks,
James

             reply	other threads:[~2011-04-02 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 23:03 James Pickens [this message]
2011-04-03  0:35 ` Background processes in post-receive hook Junio C Hamano
2011-04-03  3:22 ` Sitaram Chamarty
2011-04-03  4:59   ` Joe Ratterman
2011-04-03  5:06   ` Jonathan Nieder

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=AANLkTinrEt6DkwhknpDZ0iV9PR+7bBd3DAaPRJOgNFTG@mail.gmail.com \
    --to=jepicken@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).