From: Wladimir <laanwj@gmail•com>
To: Tom Geller <tom@tomgeller•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
Date: Mon, 3 Mar 2014 08:56:55 +0100 [thread overview]
Message-ID: <CA+s+GJC20-vKrkPhBdvHMQ5U_ocuFv_AYciPTYCexhRLsggUig@mail.gmail.com> (raw)
In-Reply-To: <E2C84BD6-CA8D-41D3-8C1E-BCCF67087F7F@tomgeller.com>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Mon, Mar 3, 2014 at 12:02 AM, Tom Geller <tom@tomgeller•com> wrote:
> Anyway, this particular solution doesn't appear to be possible in this
> case, as the file isn't at
> https://github.com/bitcoin/bitcoin/tree/0.9.0/doc/release-notes , and I
> don't believe I could copy it to the repository without going the whole git
> route. Suggestions welcome, here or privately.
>
It's not entirely trivial as you have to make sure you're editing on the
0.9 branch not the master branch, but can be done like this:
- 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'.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1441 bytes --]
next prev parent reply other threads:[~2014-03-03 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2014-03-03 9:59 ` Odinn Cyberguerrilla
[not found] <mailman.41744.1393833438.2178.bitcoin-development@lists.sourceforge.net>
2014-03-03 18:46 ` Tom Geller
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
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=CA+s+GJC20-vKrkPhBdvHMQ5U_ocuFv_AYciPTYCexhRLsggUig@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=tom@tomgeller$(echo .)com \
/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