From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: June Council meeting summary + log
Date: Sat, 17 Jun 2006 17:12:01 -0400 [thread overview]
Message-ID: <200606171712.02463.vapier@gentoo.org> (raw)
In-Reply-To: <e71oqr$771$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
On Saturday 17 June 2006 16:26, Ryan Hill wrote:
> Mike Frysinger wrote:
> > unadulterated log of the meeting will be synced out to the servers in a
> > bit: http://www.gentoo.org/proj/en/council/meeting-logs/20060616.txt
>
> I got http://www.gentoo.org/proj/en/council/meeting-logs/20060615.txt
> Also the council project page links to 20060620.txt (?).
i clearly suck at dates
everything should refer to 20060615 now, thanks
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2006-06-17 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 17:43 [gentoo-dev] June Council meeting summary + log Mike Frysinger
2006-06-17 20:26 ` [gentoo-dev] " Ryan Hill
2006-06-17 21:12 ` Mike Frysinger [this message]
2006-06-17 22:43 ` Lance Albertson
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=200606171712.02463.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox