From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Thomas Schwinge <tschwinge@gnu.org>,
samuel.thibault@gnu.org, "Jose E. Marchesi" <jemarch@gnu.org>
Subject: Re: GSoC status
Date: Wed, 23 Apr 2014 19:00:34 +0200 [thread overview]
Message-ID: <20140423170034.GB31638@debian> (raw)
In-Reply-To: <87oazsauno.fsf@yeeloong.lan>
On Wed, Apr 23, 2014 at 12:16:11PM -0400, Mark H Weaver wrote:
> FWIW, I received that message (dated Wed, 09 Apr 2014 21:28:54 +0200),
> as I was on the CC list. In fact, I received two copies of it.
I also received it. This looks like a case of very bad luck, where adding
more formal procedure would not have avoided the problem.
Andreas
next prev parent reply other threads:[~2014-04-23 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 12:32 GSoC status Ludovic Courtès
2014-04-23 16:16 ` Mark H Weaver
2014-04-23 16:48 ` Ludovic Courtès
2014-04-23 16:58 ` Jose E. Marchesi
2014-04-23 22:24 ` Ludovic Courtès
2014-04-23 22:52 ` Ludovic Courtès
2014-04-23 17:00 ` Andreas Enge [this message]
2014-04-23 21:51 ` Samuel Thibault
2014-04-23 22:39 ` Nikita Karetnikov
-- strict thread matches above, loose matches on Subject: below --
2020-01-22 23:05 Gábor Boskovits
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140423170034.GB31638@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=jemarch@gnu.org \
--cc=mhw@netris.org \
--cc=samuel.thibault@gnu.org \
--cc=tschwinge@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).