From: Sverre Rabbelier <srabbelier@gmail.com>
To: Reinier Lamers <tux_rocker@reinier.de>
Cc: git@vger.kernel.org
Subject: Re: ANNOUNCE: darcs 2.4
Date: Sat, 27 Feb 2010 13:52:14 +0100 [thread overview]
Message-ID: <fabb9a1e1002270452j78d64fcbt521fb6b782174d04@mail.gmail.com> (raw)
In-Reply-To: <c5c817ef1002270433r15132479obbce12b63596f154@mail.gmail.com>
Heya,
On Sat, Feb 27, 2010 at 13:33, Reinier Lamers <tux_rocker@reinier.de> wrote:
> I just wanted to let git developers and interested users know what
> their colleagues are up to.
Fair enough, I just thought I missed something from the announcement :).
> If sending release announcements of other
> version control systems to the git lists is generally seen as spam,
> I'll never do it again.
I don't mind myself, the email was clearly marked to be about darcs,
so if someone isn't interested in that it's easy to not read the mail.
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2010-02-27 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 12:17 ANNOUNCE: darcs 2.4 Reinier Lamers
2010-02-27 12:28 ` Sverre Rabbelier
2010-02-27 12:33 ` Reinier Lamers
2010-02-27 12:52 ` Sverre Rabbelier [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=fabb9a1e1002270452j78d64fcbt521fb6b782174d04@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=tux_rocker@reinier.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).