From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] [PATCH] shell commands are now run in a child process
Date: Fri, 29 Feb 2008 22:42:09 -0600 [thread overview]
Message-ID: <1645600603.20080229224209@rice.edu> (raw)
In-Reply-To: <1203961671-sup-8158@south>
William Morgan @ 2008-2-25 11:48:19 AM
"[sup-talk] [PATCH] shell commands are now run in a child process" <mid:1203961671-sup-8158 at south>
I've been getting more of these when playing with offlineimap. I
submitted a bug upstream:
http://ferret.davebalmain.com/trac/ticket/343
--
Christopher Warrington <chrisw at rice.edu>
Today's Oxymoron: Twelve-ounce pound cake
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 183 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080229/bc3669a5/attachment.bin
next prev parent reply other threads:[~2008-03-01 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 17:48 William Morgan
2008-03-01 4:42 ` Christopher Warrington [this message]
2008-03-01 20:37 ` William Morgan
-- strict thread matches above, loose matches on Subject: below --
2008-02-03 8:11 Christopher Warrington
2008-02-05 17:34 ` William Morgan
2008-02-05 19:29 ` Christopher Warrington
2008-02-05 20:12 ` William Morgan
2008-02-08 9:40 ` Christopher Warrington
2008-02-19 17:48 ` William Morgan
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=1645600603.20080229224209@rice.edu \
--to=chrisw@rice.edu \
/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