From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: Re: Fwd: Update-Accelerator 3.0
Date: Tue, 12 Mar 2013 13:44:26 +0100 [thread overview]
Message-ID: <trinity-ce373581-dff7-48e3-b18f-d203a0b44197-1363092266342@3capp-gmx-bs46> (raw)
In-Reply-To: <1363091107.2221.26.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
Michael,
basically you're right, but there is development just on the run in the moment.
And the intermediate results aren't to bad.
Therefore my more technical details.
And yes we should collect the proposal for features, mainly the topic "source and kind of cached material" is relevant for the decision about the technical implementation.
-Bernhard
prev parent reply other threads:[~2013-03-12 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-4fddf3b5-ccc4-4ab6-aa82-e7c38081966d-1362605012586@3capp-gmx-bs43>
2013-03-06 22:08 ` Aw: " Michael Tremer
2013-03-07 9:36 ` Aw: " Bernhard Bitsch
2013-03-07 13:15 ` Jörn-Ingo Weigert
2013-03-12 12:25 ` Michael Tremer
2013-03-12 12:44 ` Bernhard Bitsch [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=trinity-ce373581-dff7-48e3-b18f-d203a0b44197-1363092266342@3capp-gmx-bs46 \
--to=bernhard.bitsch@gmx.de \
--cc=development@lists.ipfire.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