From: Tom Geller <tom@tomgeller•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
Date: Mon, 3 Mar 2014 13:46:26 -0500 [thread overview]
Message-ID: <05EE0D18-C42A-4DCD-A3A3-18CD0B64A386@tomgeller.com> (raw)
In-Reply-To: <mailman.41744.1393833438.2178.bitcoin-development@lists.sourceforge.net>
Thanks to everyone with advice re: editing text on github, and Mt. Gox' control of the wiki. Regarding the latter, "SerajewelKS" and "gmaxwell" in IRC/bitcoin confirmed that fixes are underway, but didn't give specifics. I'll wait.
Regarding text editing, special thanks to Wladimir for the simplest solution:
> - Go to https://github.com/bitcoin/bitcoin/blob/0.9.0/doc/release-notes.md
> - Click "edit"
> - Make your changes and add a commit message describing the change, usually something like 'doc: Add missing foowidget to release notes'.
I'll try to make time to go over the 0.9.0rc2 text soon. Cheers,
---
Tom Geller * Oberlin, Ohio * 415-317-1805
Writer/Presenter * http://www.tomgeller.com
articles, marketing, videos, user guides, books
next parent reply other threads:[~2014-03-03 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.41744.1393833438.2178.bitcoin-development@lists.sourceforge.net>
2014-03-03 18:46 ` Tom Geller [this message]
2014-03-03 19:13 ` Tom Geller
2014-03-03 19:40 ` Tom Geller
2014-03-03 21:18 ` Mike Hearn
2014-03-04 19:10 ` Tom Geller
[not found] <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
2014-03-02 20:10 ` Tom Geller
2014-03-02 20:40 ` Peter Todd
2014-03-02 22:11 ` Drak
2014-03-02 23:02 ` Tom Geller
2014-03-03 6:04 ` Luke-Jr
2014-03-03 7:56 ` Wladimir
2014-03-03 9:59 ` Odinn Cyberguerrilla
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=05EE0D18-C42A-4DCD-A3A3-18CD0B64A386@tomgeller.com \
--to=tom@tomgeller$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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