All of lore.kernel.org
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Jonas Fonseca <fonseca@diku.dk>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] tig 0.8
Date: Tue, 19 Jun 2007 04:23:05 -0700	[thread overview]
Message-ID: <86zm2wmbmu.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20070619075731.GA12441@diku.dk> (Jonas Fonseca's message of "Tue, 19 Jun 2007 09:57:31 +0200")

>>>>> "Jonas" == Jonas Fonseca <fonseca@diku.dk> writes:

Jonas> A new version of tig has been released. It mainly contains bugfixes,
Jonas> most importantly for regressions in the pager mode.

I know you know what tig is.  I know *I* could figure out what
tig is by going through the mailing list, or by pulling down the
entire distro from the following:

Jonas> Get the tarball at http://jonas.nitro.dk/tig/releases/
Jonas> or pull it from git://repo.or.cz/tig.git

But 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.  My default is ignore it.

Since you have boilerplace for this, you can fix this once, and not worry
about it after that. :)

I'm saying this publicly so that other announcements might also be improved,
not that I've previously noticed any other confusion.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  reply	other threads:[~2007-06-19 11:24 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 [this message]
2007-06-19 12:41   ` Jonas Fonseca

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=86zm2wmbmu.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=fonseca@diku.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.