Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WKNkT-0000UT-GK for bitcoin-development@lists.sourceforge.net; Mon, 03 Mar 2014 07:57:17 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.179 as permitted sender) client-ip=209.85.215.179; envelope-from=laanwj@gmail.com; helo=mail-ea0-f179.google.com; Received: from mail-ea0-f179.google.com ([209.85.215.179]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WKNkD-0000bS-J4 for bitcoin-development@lists.sourceforge.net; Mon, 03 Mar 2014 07:57:17 +0000 Received: by mail-ea0-f179.google.com with SMTP id q10so4282805ead.10 for ; Sun, 02 Mar 2014 23:56:55 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.204.76.7 with SMTP id a7mr6098149bkk.17.1393833415319; Sun, 02 Mar 2014 23:56:55 -0800 (PST) Received: by 10.205.75.72 with HTTP; Sun, 2 Mar 2014 23:56:55 -0800 (PST) In-Reply-To: References: <20140302204029.GA21339@tilt> Date: Mon, 3 Mar 2014 08:56:55 +0100 Message-ID: From: Wladimir To: Tom Geller Content-Type: multipart/alternative; boundary=047d7bb03bea98d0c504f3af21f8 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline X-Headers-End: 1WKNkD-0000bS-J4 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Procedure for non-tech contributions X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2014 07:57:17 -0000 --047d7bb03bea98d0c504f3af21f8 Content-Type: text/plain; charset=UTF-8 On Mon, Mar 3, 2014 at 12:02 AM, Tom Geller 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 --047d7bb03bea98d0c504f3af21f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, 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 bran= ch, but can be done like this:

- Click "edit"
- Make your changes and add a c= ommit message describing the change, usually something like 'doc: Add m= issing foowidget to release notes'.

Wladimir

--047d7bb03bea98d0c504f3af21f8--