From: Mark Wilden <mark@mwilden.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] TopGit 0.7
Date: Thu, 5 Mar 2009 12:45:20 -0800 [thread overview]
Message-ID: <3c30da400903051245j2f89a136m95cdae3c64292024@mail.gmail.com> (raw)
In-Reply-To: <20090305202709.GB15486@pengutronix.de>
On Thu, Mar 5, 2009 at 12:27 PM, Uwe Kleine-König
<u.kleine-koenig@pengutronix.de> wrote:
>
> I'm happy to announce that TopGit 0.7 was released today.
>
> This release brings you several bug fixes and a few new features.
When announcing a release, you might consider including a few words
about what the project does. There will be people (like me) who were
not familiar with it before seeing the release announcement, and this
would help them to quickly find out whether it should be investigated.
Just a suggestion - ignore at will. :)
///ark
next prev parent reply other threads:[~2009-03-05 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 20:27 [ANNOUNCE] TopGit 0.7 Uwe Kleine-König
2009-03-05 20:31 ` Uwe Kleine-König
2009-03-05 20:45 ` Mark Wilden [this message]
2009-03-06 2:04 ` Mark Wilden
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=3c30da400903051245j2f89a136m95cdae3c64292024@mail.gmail.com \
--to=mark@mwilden.com \
--cc=git@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.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).