From: Thomas Harning <harningt@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: git@vger.kernel.org
Subject: Re: git-daemon: single-line logging
Date: Sun, 16 Nov 2008 11:08:42 -0500 [thread overview]
Message-ID: <F8349F16-7ABA-4C00-9AE3-F579197D27B8@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0811131749420.16134@fbirervta.pbzchgretzou.qr>
On Nov 13, 2008, at 11:51 AM, Jan Engelhardt wrote:
> I wrote this patch for my git-daemon to make it much easier to parse
> /var/log/git-daemon.log -- namely reducing the output from three lines
> per connected client to just one.
I think that this is a pretty good change, I'll have to try it out...
One thing I noticed was that there was some information lost in-
transition...
The immediate information lost that I see is the port used.
prev parent reply other threads:[~2008-11-16 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 16:51 git-daemon: single-line logging Jan Engelhardt
2008-11-16 16:08 ` Thomas Harning [this message]
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=F8349F16-7ABA-4C00-9AE3-F579197D27B8@gmail.com \
--to=harningt@gmail.com \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
/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