From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-daemon: timeout, eliminate double DWIM
Date: Thu, 20 Oct 2005 03:26:15 +0200 [thread overview]
Message-ID: <20051020012615.GU30889@pasky.or.cz> (raw)
In-Reply-To: <7vsluxvvdc.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Thu, Oct 20, 2005 at 03:18:39AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> Petr Baudis <pasky@suse.cz> writes:
>
> > You didn't update Documentation/git-daemon.txt.
> >...
> > Ditto.
>
> Patches welcome.
Ah, I didn't notice it was already merged, sorry.
BTW, some of the commits in your tree have the same author and
committer date while they shouldn't:
author H. Peter Anvin <hpa@zytor.com> Wed, 19 Oct 2005 14:27:01 -0700
committer Junio C Hamano <junkio@cox.net> Wed, 19 Oct 2005 14:27:01 -0700
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
prev parent reply other threads:[~2005-10-20 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 18:54 [PATCH] git-daemon: timeout, eliminate double DWIM H. Peter Anvin
2005-10-20 0:28 ` Petr Baudis
2005-10-20 1:18 ` Junio C Hamano
2005-10-20 1:26 ` Petr Baudis [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=20051020012615.GU30889@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).