From: Junio C Hamano <junkio@cox.net>
To: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.1.4
Date: Wed, 09 May 2007 01:49:42 -0700 [thread overview]
Message-ID: <7v3b26wfdl.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070509083234.GD5294@informatik.uni-freiburg.de> (Uwe Kleine-König's message of "Wed, 9 May 2007 10:32:35 +0200")
Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de> writes:
> Hello Junio,
>
> you either overlooked my mail "Documentation Bugs"[1] or you choosed to
> ignore it :-( Note that the second issue was only me being stupid.
The best way to prod busy maintainer is to resend an applicable
patch, not sending a URL. Thanks.
prev parent reply other threads:[~2007-05-09 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 7:10 [ANNOUNCE] GIT 1.5.1.4 Junio C Hamano
2007-05-09 8:32 ` Uwe Kleine-König
2007-05-09 8:49 ` Junio C Hamano [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=7v3b26wfdl.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ukleinek@informatik.uni-freiburg.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;
as well as URLs for NNTP newsgroup(s).