Hi Matej,<div><br></div><div>I would normally have created a pull request, but I thought it would be far simpler for somebody with commit privilege to just add one new file rather than go through the whole fork/clone/checkout/commit.....pull request process, but I hadn't thought of blame, so I will do it the long way as you suggested.</div>
<div><br></div><div>Martin<br><br><div class="gmail_quote">On 9 November 2012 21:06, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Many thanks! (and for your follow-up.)<br>
<div class="HOEnZb"><div class="h5"><br>
On Nov 9, 2012, at 3:05 PM, Matěj Cepl <<a href="mailto:mcepl@redhat.com">mcepl@redhat.com</a>> wrote:<br>
<br>
> On Fri, 2012-11-09 at 12:51 -0500, DM Smith wrote:<br>
>> Would you provide a walk-through of the best practices of creating a<br>
>> branch, making a change to the branch, and creating/submitting a pull<br>
>> request?<br>
><br>
> 1) create an account on Github and login<br>
> 2) Go to <a href="https://github.com/crosswire/jsword/fork" target="_blank">https://github.com/crosswire/jsword/fork</a> (button Fork) and wait<br>
> until fork is done<br>
> 3) clone that repo, e.g., something like<br>
> git clone git@github.com:yourusername/jsword.git<br>
> 4) cd jsword<br>
> 5) git checkout -b name-of-new-branch master<br>
> 6) edit, edit, compile, edit, ...<br>
> 7) git commit -a -v<br>
> In the text editor you get, review the diff below to be sure,<br>
> everythng is as it supposed to be, and on the top of the file write a<br>
> brief explanatory commit message in the format<br>
><br>
> one-line-not-more-than-80-chars-as-a-headline<br>
><br>
> Longer explanation of changes you've made (could be many lines long, but<br>
> it keep lines under 80 characters each).<br>
><br>
> 8) Save the commit message and leave the editor<br>
> 9) git push origin name-of-new-branch<br>
> 10) Go to<br>
> <a href="https://github.com/yourusername/jsword/tree/name-of-your-branch" target="_blank">https://github.com/yourusername/jsword/tree/name-of-your-branch</a> (switch<br>
> branches)<br>
> 11) and then <a href="https://github.com/yourusername/jsword/pull/new/master" target="_blank">https://github.com/yourusername/jsword/pull/new/master</a><br>
> (create a new pull request)<br>
><br>
> The same thing can be done from many IDEs with some GUI stuff, but it is<br>
> hard to explain in email.<br>
><br>
> Best,<br>
><br>
> Matěj<br>
><br>
> --<br>
> <a href="http://www.ceplovi.cz/matej/" target="_blank">http://www.ceplovi.cz/matej/</a>, Jabber: mcepl<at><a href="http://ceplovi.cz" target="_blank">ceplovi.cz</a><br>
> GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC<br>
><br>
> Our lives are spectacles of powerlessness.<br>
> -- Richard Rohr<br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> jsword-devel mailing list<br>
> <a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br>
<br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</div></div></blockquote></div><br></div>