From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-daemon: Simplify child management and associated logging by
Date: Wed, 13 Aug 2008 09:36:13 +0200 [thread overview]
Message-ID: <20080813073613.GB12628@cuci.nl> (raw)
In-Reply-To: <7vvdy5pxz6.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
>"Stephen R. van den Berg" <srb@cuci.nl> writes:
>> Separating it causes two things:
>> a. The patches to become dependent on each other in the timeline.
>> b. More (redundant) work, because some parts that need to be rewritten, get
>> deleted by the following patch(es).
>These are actually desirable properties from reviewability point of view.
Ok, I'll look into the splitup.
>>> - I see you have a call to vsyslog, which is the first user of the
>>> function. How portable is it (the patch coming from you, I know
>>> Solaris would have it, and recent 4BSD also would, but what about the
>>> others)?
>> Cygwin has it, Solaris does, Linux does, MacOSX does.
>> AIX and HPUX don't, perhaps.
>> I'll see what I can do to avoid it, yet simplify the code.
>That's one of the reasons why I asked you to split it to three patches, so
>that the syslog change can potentially be independently replaced with a
>better alternative.
Well, I've already found an alternative, and looks a lot more appealing
than the buffer-juggling code of before.
>In any case, it is already late in the rc cycle; I'd like to apply your
>earlier "In SysV, signal(SIGCHLD) need to be rearmed" patch and nothing
>else for now. The clean-up is very attractive but can be done post 1.6.0.
No problem. That's the reason I chipped that first patch off; it's a
direct bugfix. And BTW, don't mistake me for a "Solaris guy". I've
been using Linux almost exclusively since 1991. My SunOS/Solaris knowledge
has been fading steadily ever since. It's just that I had to install
git-daemon on someone else's Solaris box just recently.
--
Sincerely,
Stephen R. van den Berg.
"And now for something *completely* different!"
next prev parent reply other threads:[~2008-08-13 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 19:36 [PATCH] git-daemon: SysV needs the signal handler reinstated Stephen R. van den Berg
2008-08-12 21:25 ` [PATCH] git-daemon: Simplify child management and associated logging by Stephen R. van den Berg
2008-08-12 22:05 ` Junio C Hamano
2008-08-12 22:56 ` Stephen R. van den Berg
2008-08-12 23:52 ` Stephen R. van den Berg
2008-08-13 0:03 ` Stephen R. van den Berg
2008-08-13 0:07 ` Marcus Griep
2008-08-13 0:20 ` Junio C Hamano
2008-08-13 7:36 ` Stephen R. van den Berg [this message]
2008-08-13 8:23 ` Stephen R. van den Berg
2008-08-13 19:28 ` Junio C Hamano
2008-08-12 22:32 ` Alex Riesen
2008-08-12 23:12 ` Stephen R. van den Berg
2008-08-13 6:20 ` Alex Riesen
2008-08-13 7:21 ` Stephen R. van den Berg
2008-08-13 6:41 ` Andreas Ericsson
2008-08-13 7:18 ` Alex Riesen
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=20080813073613.GB12628@cuci.nl \
--to=srb@cuci.nl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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