From: Stefan Thomas <moon@justmoon.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Wiki
Date: Thu, 27 Oct 2011 19:18:02 +0200 [thread overview]
Message-ID: <4EA9924A.2000308@justmoon.de> (raw)
In-Reply-To: <CAHY2ayAB1xGVMgs0WaTEoUj=Q6LvdmTV+12Y8yEb4-Ep8Bb28g@mail.gmail.com>
+1 for something based on git. Github has a dedicated wiki feature that
is git-backed:
https://github.com/bitcoinjs/node-bitcoin-p2p/wiki/
git://github.com/bitcoinjs/node-bitcoin-p2p.wiki.git
On 10/27/2011 6:15 PM, Daniel F wrote:
> +1 on git. not necessarily as replacement, but at least as backup.
> could possibly use markdown and github pages, which automagically
> pushes git commits out to the website (uses markdown syntax, iirc)
>
> On Thu, Oct 27, 2011 at 11:22 AM, Nils Schneider<nils@nilsschneider.net> wrote:
>> Can we use a git repo or something more redundant for BIPs? They're
>> rather important and the wiki has been unreliable before.
>>
>> On 27.10.2011 17:15, Amir Taaki wrote:
>>> Anybody know how to contact MT about getting it back online? I still
>>> haven't finished copy-editing the BIPs and need access to them since
>>> there's a new one to be added.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> The demand for IT networking professionals continues to grow, and the
>>> demand for specialized networking skills is growing even more rapidly.
>>> Take a complimentary Learning@Cisco Self-Assessment and learn
>>> about Cisco certifications, training, and career opportunities.
>>> http://p.sf.net/sfu/cisco-dev2dev
>>>
>>>
>>>
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>> ------------------------------------------------------------------------------
>> The demand for IT networking professionals continues to grow, and the
>> demand for specialized networking skills is growing even more rapidly.
>> Take a complimentary Learning@Cisco Self-Assessment and learn
>> about Cisco certifications, training, and career opportunities.
>> http://p.sf.net/sfu/cisco-dev2dev
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
prev parent reply other threads:[~2011-10-27 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 15:15 [Bitcoin-development] Bitcoin Wiki Amir Taaki
2011-10-27 15:22 ` Nils Schneider
2011-10-27 16:15 ` Daniel F
2011-10-27 17:12 ` Christian Decker
2011-10-27 17:18 ` Stefan Thomas [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=4EA9924A.2000308@justmoon.de \
--to=moon@justmoon.de \
--cc=bitcoin-development@lists.sourceforge.net \
/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