From: Jonas Fonseca <fonseca@diku.dk>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] tig 0.8
Date: Tue, 19 Jun 2007 14:41:33 +0200 [thread overview]
Message-ID: <20070619124133.GA22215@diku.dk> (raw)
In-Reply-To: <86zm2wmbmu.fsf@blue.stonehenge.com>
Randal L. Schwartz <merlyn@stonehenge.com> wrote Tue, Jun 19, 2007:
> [...] an affect announcement of "tig" (even an update release) should probably
> include at least one sentence of what it is, so I can decide whether to be
> interested or ignore it.
Yeah, you are right. I got the hint from a cgit release not so long ago
that was also "blamed" for lacking a small project introduction. I was
in a hurry and forgot all about it this morning ...
--
Jonas Fonseca
prev parent reply other threads:[~2007-06-19 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 7:57 [ANNOUNCE] tig 0.8 Jonas Fonseca
2007-06-19 11:23 ` Randal L. Schwartz
2007-06-19 12:41 ` Jonas Fonseca [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=20070619124133.GA22215@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
/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).