Hi,
This weekend I closed some old github issues that are no longer
reproducible in more recent versions, or needed input from the submitter
but were stalling for months.
I've also closed some issues that deal purely with Wx UI issues like this
one:
https://github.com/bitcoin/bitcoin/issues/425
, John Smith wrote:
> Those indeed seems weird... I'll take a look at it.
>
> JS
>
>
> On Mon, Oct 24, 2011 at 8:55 PM, Geir Harald Hansen <
> opera...@bitminter.com> wrote:
>
>> Three quick examples of duplicated strings. There are many more. Some of
&
> Better would be a GUI=0/1 option to the bitcoin-qt.pro until a nicer
> (ideally
> automake/autoconf) system is implemented...
>
Are you sure you want to require qmake for the daemon build?
I agree having a unified build system would be nice, but qmake doesn't add
anything for non-qt software. B
ck, it was broadcast to the network to be added to the
> block chain. If it fails to get into the chain, it will change to "not
> accepted" and not be spendable. This may occasionally happen if another
> node generates a block within a few seconds of yours.
>
> Regards,
>
a coding (PushMessage,
> bignum and serialize stuff).
>
> No need to worry about that :)
>
> ------
> *From:* John Smith
> *To:* theymos
> *Cc:* bitcoin-development@lists.sourceforge.net
> *Sent:* Monday, October 24, 2011 6:02 AM
> *Subject:* Re
Indeed. It could make sense. That's the reason why Qt distinguishes strings
based on context as well as content.
But it could also be nonsense. Can you be more specific as to which strings?
JS
On Mon, Oct 24, 2011 at 1:24 PM, Christian Decker <
decker.christ...@gmail.com> wrote:
> Actually no,
Yes, I know that. It compiles.
If we pulled all the 'This is legal in C++' tricks in the bitcoin source it
would be even less maintainable and readable than now. But whatever...
JS
On Sun, Oct 23, 2011 at 10:51 PM, theymos wrote:
> It's legal for a scope to define variables with names that con
FYI
It's in a disabled feature (replacement), so I'm not sure how important this
is, but it doesn't look good.
-- Forwarded message --
From: Dean Gores
Date: Sun, Oct 23, 2011 at 11:15 AM
Subject: bitcoin scope issue in main.cpp
To: laa...@gmail.com
You have "i" and "output" dec
Hello Brian,
There are no unit tests for the Qt GUI code itself as of this moment.
The tests for the bitcoin core are still there in src/tests >). You need to
build them with the makefile, though. qmake is currently only used for the
GUI executable.
JS
On Mon, Oct 3, 2011 at 11:04 PM, Brian McQ
On Thu, Sep 29, 2011 at 12:49 PM, solar wrote:
> It's just simple SHA2, you can implement the whole thing easily without
> dragging in a huge lib like OpenSSL. I guess I haven't looked at it
> recently but the original CPU miner was just implemented locally in bitcoin
> and didn't use any libs.
Nils,
Sounds good. I'm also doubtful of depending on two crypto libraries when
OpenSSL does perfectly well.
However, losing compatibility with miners is not very nice. Is there really
not a way to compute midstate with OpenSSL?
JS
On Mon, Sep 26, 2011 at 7:42 PM, Nils Schneider wrote:
> Hey,
>
2011/9/22 Martinx - ジェームズ
> Hi everybody!!
>
> This is my first message here... I'm ThiagoCMC at bitcointalk...
>
> Well, one of the features that I like most is that, every time I receive
> some Bitcoin amount, a new address appear at my "AddressBook"automatically,
> AND, I like to track it.
>
> Fixing (2) is easier; incorporating a ntp library and/or simply
> removing the bitcoin mining code from the client but requiring pools
> and miners to have accurate-to-within-a-minute system clocks (or their
> blocks will be "discouraged") seems reasonable to me.
Incorporating NTP seems overkil
Alex,
On Sun, Sep 11, 2011 at 7:45 AM, Alex Waters wrote:
> Hey John,
>
> It could be as simple as listing some things that you think could possibly
> break if qt is implemented. For example, "check the UI for artifacts". I
> don't really know what could potentially need to be tested, so any hel
Hello Alex,
On Sun, Sep 11, 2011 at 12:20 AM, Alex Waters wrote:
> Can you please submit a pull request and testing plan? If these already
> exist, can you please link them here?
What testing plan do you need?
JS
--
U
On Fri, Sep 9, 2011 at 6:57 AM, Luke-Jr wrote:
> On Eligius, I have two bitcoinds running on the same system:
> - a hub node, which is dedicated to relaying network activity between the
> hundreds of nodes Eligius peers with
> - a work node, which is dedicated to managing mining, and only ever
>
Be careful though, if you relay everything, it suddenly *does* have DDoS
potential...
JS
On Thu, Sep 8, 2011 at 5:15 PM, Luke-Jr wrote:
> On Thursday, September 08, 2011 12:51:02 PM Mike Hearn wrote:
> > Bitcoin is one of the few pieces of software I use that has no concept of
> > automatic up
There is a lot of complaining about this alert system, but I really don't
see the problem.
As others have already said, it's just a message. Even if someone managed to
compromise the private key, the most they could do is spam graffiti messages
or try phishing. There are much worse things that cou
On Fri, Sep 2, 2011 at 8:12 PM, Gavin Andresen wrote:
> Bitcoin version 0.4 release candidate 1 is ready for initial testing;
> please grab the source from github and try to break it.
>
> The big, visible change is wallet private key encryption, which is NOT
> turned on by default.
>
> The big, in
On Fri, Sep 2, 2011 at 8:32 PM, Rob Meijer wrote:
> Given that there was not a single response to my post, I gather there is
> no to little interest in an updated MinorFs that could be used by bitcoin
> on systems that support AppArmor (Ubuntu and OpenSuse).
>
Oh yes there is interest. I meant t
On Thu, Sep 1, 2011 at 2:13 AM, Luke-Jr wrote:
> On Wednesday, August 31, 2011 10:20:48 AM John Smith wrote:
> > The project builds on Windows, MacOSX and Linux using qmake.
>
> How do you set build options with qmake?
>
You can put assignments on the commandline; for examp
Would it be possible to port some of the existing translations?
>
Well, the strings in the core can be reused one-on-one as the _ function is
mapped to the Qt translation function.
And some of the UI texts probably can be reused as well, at least for a
rough approximation.
The files will have to
Hi,
Bitcoin-qt is now feature complete (including wallet encryption), and has
been tested for a while by various people without any major problems.
It is now in status of feature freeze.
The project builds on Windows, MacOSX and Linux using qmake.
Impact to the core bitcoin functions is still m
23 matches
Mail list logo
