From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core120 update problem
Date: Mon, 05 Mar 2018 16:21:10 +0100 [thread overview]
Message-ID: <1520263270.7449.4.camel@ipfire.org> (raw)
In-Reply-To: <1519975477.7068.16.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
Hi all,
fast feedback causing this topic, have build tor-0.3.3.2-alpha which
worked without problems, have then seen that tor-0.3.2.10 has also been
released, have build it and tested it too in Core 120 environment and
it starts and seems also to work again without problems.
Greetings,
UE
prev parent reply other threads:[~2018-03-05 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1519839393.6593.5.camel@ipfire.org>
2018-03-01 21:03 ` Michael Tremer
2018-03-02 7:24 ` ummeegge
2018-03-05 15:21 ` ummeegge [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=1520263270.7449.4.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--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