From: Gerrit Pape <pape@smarden.org>
Subject: Re: new "sv status" flags and exit-tracking patch, and misc.
Date: Mon, 26 Sep 2005 10:12:20 +0000 [thread overview]
Message-ID: <20050926100729.10530.qmail@c13d51208eed48.315fe32.mid.smarden.org> (raw)
In-Reply-To: <dgn2ks$usn$1@sea.gmane.org>
On Mon, Sep 19, 2005 at 02:13:30PM -0500, Charles Duffy wrote:
> Charles Duffy wrote:
> >Attached is a patch which attempts to stick to the items we agreed on.
>
> Erk -- actually, that one was a little too overreaching as well, since
> it changed "sv status" to provide the last exit status of finish (if
> curently in run) or run (if currently in finish), if that program exited
> with a status other than 0. Since the requested spec was that the output
> of "sv status" (when called without flags) not be altered... well,
> here's another attempt.
Hi Charles, thanks a lot for the patch. This looks much better to me to
work with. I'll try to find some time soon, to review it, and integrate
it into the next runit test version. Thanks also for arranging with the
coding style of the runit project, it may well be that's a strange style
I use, but it's one I personally can read well and work good with.
Regards, Gerrit.
next prev parent reply other threads:[~2005-09-26 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 4:46 Charles Duffy
2005-09-17 5:17 ` Mike Bell
2005-09-19 8:35 ` Gerrit Pape
2005-09-17 8:53 ` Laurent Bercot
2005-09-19 8:31 ` Gerrit Pape
2005-09-19 16:04 ` Charles Duffy
2005-09-19 19:13 ` Charles Duffy
2005-09-21 21:50 ` new "sv status" flags and exit-tracking patch, yet again Charles Duffy
2005-09-26 10:12 ` Gerrit Pape [this message]
2005-09-26 15:31 ` duplicate processes Jussi Ramo
2005-09-26 15:42 ` Charlie Brady
2005-12-08 11:08 ` new "sv status" flags and exit-tracking patch, and misc Gerrit Pape
2005-12-08 19:37 ` Charles Duffy
2005-12-09 14:29 ` Gerrit Pape
2005-12-09 14:50 ` Rafal Bisingier
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=20050926100729.10530.qmail@c13d51208eed48.315fe32.mid.smarden.org \
--to=pape@smarden.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).