From: Matt Corallo <bitcoin-list@bluematt.me>
To: Oliver Egginger <bitcoin@olivere.de>,
Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Ubuntu LTS Packaging?
Date: Sat, 12 Apr 2014 11:34:46 -0400 [thread overview]
Message-ID: <1fe5b0bb-c2f4-4edf-99c3-4305498418bc@email.android.com> (raw)
In-Reply-To: <53494CFF.1030303@olivere.de>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Hmm? It's up to date... 0.9.1 doesn't change anything for dynamically-linked-to-openssl builds.
Matt
On April 12, 2014 10:26:07 AM EDT, Oliver Egginger <bitcoin@olivere.de> wrote:
>Hello,
>
>so far, nothing yet?
>
>See: https://launchpad.net/~bitcoin/
>
>I'm developing currently a LiveCD for hot/cold wallet management on
>Ubuntu LTS basis. For critical vulnerabilities I have to provide timely
>updates. I have now decided to maintain my own repository for this
>project. If there are better alternatives, let me know.
>
>regards
>Oliver
>
>------------------------------------------------------------------------------
>Put Bad Developers to Shame
>Dominate Development with Jenkins Continuous Integration
>Continuously Automate Build, Test & Deployment
>Start a new project now. Try Jenkins in the cloud.
>http://p.sf.net/sfu/13600_Cloudbees
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 1472 bytes --]
next prev parent reply other threads:[~2014-04-12 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 14:26 [Bitcoin-development] Ubuntu LTS Packaging? Oliver Egginger
2014-04-12 14:35 ` Wladimir
2014-04-12 14:43 ` Luke-Jr
2014-04-12 15:34 ` Matt Corallo [this message]
2014-04-12 16:33 ` Oliver Egginger
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=1fe5b0bb-c2f4-4edf-99c3-4305498418bc@email.android.com \
--to=bitcoin-list@bluematt.me \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=bitcoin@olivere.de \
/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