From: "Luke-Jr" <luke@dashjr•org>
To: Mike Hearn <mike@plan99•net>
Cc: Pieter Wuille <pieter.wuille@cs•kuleuven.be>,
bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Version bytes "2.0"
Date: Tue, 13 Dec 2011 10:43:18 -0500 [thread overview]
Message-ID: <201112131043.19906.luke@dashjr.org> (raw)
In-Reply-To: <CANEZrP3EpkCaK2nXXazX-D-a0yO_3SkWXg74V2zh+nCM=Ko20w@mail.gmail.com>
On Tuesday, December 13, 2011 6:07:17 AM Mike Hearn wrote:
> That's cool. I hope Matts change gets merged soon. Then the issue becomes
> how do people find out about this capability? Expecting people to learn how
> to hand-craft Bitcoin links won't work.
Bitcoin-Qt 0.6 will include a QR Code generator.
> But all modern operating systems support copy/paste and drag/drop of rich
> content.
No, not really. I've found that dragging and dropping links manages to corrupt
them most of the time.
prev parent reply other threads:[~2011-12-13 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 21:10 Luke-Jr
2011-12-06 21:28 ` Luke-Jr
2011-12-10 18:16 ` Luke-Jr
[not found] ` <20111212205559.GA16665@ulyssis.org>
2011-12-12 20:57 ` Pieter Wuille
2011-12-12 21:02 ` Luke-Jr
2011-12-13 10:38 ` Mike Hearn
2011-12-13 10:56 ` Wladimir
2011-12-13 11:07 ` Mike Hearn
2011-12-13 11:15 ` Wladimir
2011-12-13 15:43 ` Luke-Jr [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=201112131043.19906.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
--cc=pieter.wuille@cs$(echo .)kuleuven.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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