John, Thanks for the Yoda-like confirmation. Glad that it worked.
For what it’s worth, the light that went on was that I needed to watch carefully which repository (mine vs. the origin) and which branch (maint/master/my branches) were selected. I also was not noticing that Github changes from my forked repository to the origin when I issue a pull request; this change in perspective is disconcerting if you don’t recognize it. Finally, before I go and do anything else, what exact steps do I need to do on my end to ensure that my fork is synced with the origin? It would be nice not to nuke everything again because I messed up my fork. David > On Sep 16, 2016, at 11:41 PM, John Ralls <[email protected]> wrote: > > >> On Sep 16, 2016, at 9:35 AM, David T. <[email protected]> wrote: >> >> Well, now. A little light may have leaked into the vast black hole that is >> my brain. I may have just caused two patches to head upstream, like >> optimistic salmon heading to their ritualized spawning grounds. One for bug >> 769457, and one for bug 687290. >> >> Of course, I could be wrong… > > David, > > Upstream they are, committed just in time for the 2.6.14 release! > > Regards, > John Ralls > _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
