From: Christopher Friedt <chrisfriedt@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Re: manually creating manifests with RESTRICT="fetch"
Date: Sat, 13 Aug 2011 10:23:45 -0400 [thread overview]
Message-ID: <CAF4BF-QQKLn2hUqA480MmjcCcLSryp_X13qCE+4s6aP-xOpOdw@mail.gmail.com> (raw)
In-Reply-To: <CAF4BF-QpJ2WvkDKH04-OezKG18fH59yHg+Ptpvw9SSambuTUnQ@mail.gmail.com>
Odd... now that I'm trying it again, it's working fine... and I
haven't even touched my PC since yesterday except for email.
Oh well - problem solved in any case.
C
On Sat, Aug 13, 2011 at 8:26 AM, Christopher Friedt
<chrisfriedt@gmail.com> wrote:
> On Sat, Aug 13, 2011 at 8:17 AM, Peter Volkov <pva@gentoo.org> wrote:
>> Oh, no! :) Bug reports should go to bugs.gentoo.org.
>
> Well... I was hoping I could just let this one slide by ... but ok
>
> C
>
prev parent reply other threads:[~2011-08-13 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 18:48 [gentoo-embedded] manually creating manifests with RESTRICT="fetch" Christopher Friedt
2011-08-12 18:55 ` [gentoo-embedded] " Christopher Friedt
2011-08-12 21:23 ` Kfir Lavi
2011-08-12 23:00 ` Christopher Friedt
2011-08-13 7:14 ` Kfir Lavi
2011-08-13 12:17 ` Peter Volkov
2011-08-13 12:26 ` Christopher Friedt
2011-08-13 14:23 ` Christopher Friedt [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=CAF4BF-QQKLn2hUqA480MmjcCcLSryp_X13qCE+4s6aP-xOpOdw@mail.gmail.com \
--to=chrisfriedt@gmail.com \
--cc=gentoo-embedded@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