OK. So, that reference is to an attempt I made to try and clear up the problems I had with getting my old repository up to date. This was a patch from February that you altered the tags on, which I was not able to convince git to move past because my patch conflicted with the applied patch. You had mentioned needing to fix that (somehow), but when I tried your fixes, they didn’t work (somehow). Because I couldn’t get git to move forward, I decided to start over.
Actually, I was referring to https://github.com/sunfish62/gnucash-docs/commit/54f29a936162f6a9172c801d77f40e5a799f4b97 <https://github.com/sunfish62/gnucash-docs/commit/54f29a936162f6a9172c801d77f40e5a799f4b97> So, I guess the answer is “No.” As in, “No, David, you didn’t get the patch committed." David > On Sep 16, 2016, at 8:54 PM, David T. via gnucash-devel > <gnucash-devel@gnucash.org> wrote: > > John, > > To say I am confused would of course be redundant. I deleted everything, and > then re-forked the Gnucash-docs to my own github account. Then I created my > local repository and created the new branch there. I thought I was recreating > the same situation I had before—but with a new copy of the docs. Is there > something more I need to do to allow you to pull from my newly-created fork? > > David > >> On Sep 16, 2016, at 7:42 PM, John Ralls <jra...@ceridwen.us> wrote: >> >> >>> On Sep 16, 2016, at 5:43 AM, David T. via gnucash-devel >>> <gnucash-devel@gnucash.org> wrote: >>> >>> Hello, >>> >>> As I mentioned earlier on a different thread, I reset my git documentation >>> installation so that I can git going again on updating the documentation. I >>> have now finished work on Bug 687290, and committed it. Can a True >>> Developer let me know whether I succeeded in getting this fix into the >>> documentation stream? >> >> David, >> >> Well, there's a pull request [1] with your patch, but you removed your >> repository from Github so the only way for me to apply it is to >> copy-and-paste (or read-and-type) it from the screen. Fortunately it's a >> small patch so that's practical, but it would have been better if you'd left >> the repository there for me to pull from. >> >> Regards, >> John Ralls >> >> [1] https://github.com/Gnucash/gnucash-docs/pull/61 > > > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel