From: Tilman Sauerbeck <tilman@code-monkey.de>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.4.0
Date: Sun, 11 Jun 2006 00:05:22 +0200 [thread overview]
Message-ID: <20060610220519.GA6354@code-monkey.de> (raw)
In-Reply-To: <7vmzckhfsx.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
Junio C Hamano [2006-06-10 14:16]:
> git-htmldocs-1.4.0.tar.{gz,bz2} (preformatted documentation)
> git-manpages-1.4.0.tar.{gz,bz2} (preformatted documentation)
Thanks! :)
Regards,
Tilman
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-10 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 21:16 [ANNOUNCE] GIT 1.4.0 Junio C Hamano
2006-06-10 22:05 ` Tilman Sauerbeck [this message]
2006-06-10 22:37 ` Paolo Ciarrocchi
2006-06-10 22:47 ` Paolo Ciarrocchi
2006-06-10 23:42 ` Junio C Hamano
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=20060610220519.GA6354@code-monkey.de \
--to=tilman@code-monkey.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).