|
From: | Ernst Reissner |
Subject: | Re: commit |
Date: | Fri, 22 Jul 2016 00:09:35 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 |
On 07/21/2016 11:57 PM, Mike Miller
wrote:
On Thu, Jul 21, 2016 at 22:10:21 +0200, Ernst Reissner wrote:Hi Mike, in the meantime i realized my failure: hg commit just commits locally. I did so and then I again cloned my environment without realizing that that discarded all my changes. Tatsuro told me that if I want to provide a patch I have to hg export. Tank you for explaining all..Thank you for your contribution. I wonder what we could add to our documentation or web site to make the contribution process more clear to new contributors like you. Any thoughts? What did you read that gave you enough to know you had to `hg commit` but not that commits are local and have to be exported or pushed? I think, https://www.gnu.org/software/octave/get-involved.html is a good start point. in particular, there is a reference to I think at least for me it would have helped to mention not only
pull from repo and resync, but also how to provide patches. Also the distinction between bugfix and other patches.
Is it also possible to add documentation? txi and within source
code? I ask because the java classes are almost not at all documented.
|
[Prev in Thread] | Current Thread | [Next in Thread] |