git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #07; Sat, 23)
Date: Sun, 24 Aug 2008 12:16:12 -0700	[thread overview]
Message-ID: <7vd4jymdfn.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0808241955550.24820@pacific.mpi-cbg.de.mpi-cbg.de> (Johannes Schindelin's message of "Sun, 24 Aug 2008 20:12:43 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> * sb/daemon (Thu Aug 14 20:02:20 2008 +0200) 4 commits
>>  - git-daemon: rewrite kindergarden, new option --max-connections
>>  - git-daemon: Simplify dead-children reaping logic
>>  - git-daemon: use LOG_PID, simplify logging code
>>  - git-daemon: call logerror() instead of error()
>> 
>> Can somebody who actually runs the daemon standalone comment on this 
>> one?
>
> I am somewhat uneasy about running my production machine with these 
> changes, since the last commit (the one introducing a kindergarden with 
> cradles) is too unobvious for me.

Well, I didn't ask anybody to _run_ it.

I asked people who care about their daemons to comment on the change, so
that if there are any issues in the code that I didn't see, the breakage
gets caught before it propagates to their daemons they build from 'next'
or 'master'.

Having said that, I do agree that the kindergarden change is very involved
(it removes more code than it adds --- the reduction of lines is somewhat
inflated because quite a lot of comments that have become stale gets
removed by the patch).

  reply	other threads:[~2008-08-24 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24  3:38 What's cooking in git.git (Aug 2008, #07; Sat, 23) Junio C Hamano
2008-08-24  4:00 ` Maintaining "needswork" section of "What's (not) cooking" Junio C Hamano
2008-08-24 18:12 ` What's cooking in git.git (Aug 2008, #07; Sat, 23) Johannes Schindelin
2008-08-24 19:16   ` Junio C Hamano [this message]
2008-08-24 20:24     ` Junio C Hamano
2008-08-24 20:27       ` [PATCH 1/3] daemon.c: minor style fixup Junio C Hamano
2008-08-24 20:27       ` [PATCH 2/3] daemon.c: simplify add_child() and kill_some_child() logic Junio C Hamano
2008-08-24 20:33       ` [PATCH 3/3] daemon.c: make sure kill_some_child() really kills somebody Junio C Hamano
2008-08-25 16:32       ` What's cooking in git.git (Aug 2008, #07; Sat, 23) Stephen R. van den Berg
2008-08-25 20:19         ` Junio C Hamano
2008-08-25 21:27           ` Stephen R. van den Berg

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=7vd4jymdfn.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --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.
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).