public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Fikret AKIN <info@fikretakin.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin ATM
Date: Fri, 20 Feb 2015 18:36:27 +0100	[thread overview]
Message-ID: <CANEZrP19rR6phzzWXS75NVuKhZbPhzL1r33xRe1nV_cuSTmtsA@mail.gmail.com> (raw)
In-Reply-To: <000201d04d29$0451ec20$0cf5c460$@fikretakin.com>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hi Fikret,

This is the wrong mailing list for such questions. Most Bitcoin ATM's are
commercial products anyway and don't accept contributors. If you find one
that is different, it's better to contact them directly.



On Fri, Feb 20, 2015 at 5:19 PM, Fikret AKIN <info@fikretakin.com> wrote:

> Hello,
>
> I want to improve the Bitcoin ATM, which way do you think I should
> continue Do you have suggestions?
>
>
>
>
>
> Thanks,
>
> Fikret AKIN
>
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

[-- Attachment #2: Type: text/html, Size: 2200 bytes --]

      reply	other threads:[~2015-02-20 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 16:19 [Bitcoin-development] Bitcoin ATM Fikret AKIN
2015-02-20 17:36 ` Mike Hearn [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=CANEZrP19rR6phzzWXS75NVuKhZbPhzL1r33xRe1nV_cuSTmtsA@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=info@fikretakin.com \
    /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