Re: Confirming Action

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

Re: Broken gnucash-docs (help / it )

Good to know. Thanks! On Fri, Sep 16, 2016 at 12:39 PM, John Ralls wrote: > > > On Sep 16, 2016, at 9:39 AM, Brad Hanks wrote: > > > > xml2po is going to pull all the translatable data out of the xml file > and put it in a .pot format. > > Brad, > > Yes,

Re: Confirming Action

> On Sep 16, 2016, at 9:35 AM, David T. 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

Re: Broken gnucash-docs (help / it )

> On Sep 16, 2016, at 9:39 AM, Brad Hanks wrote: > > xml2po is going to pull all the translatable data out of the xml file and put > it in a .pot format. Brad, Yes, that's one thing xml2po does. It does other things too, including what we use it for: Merge the document's

Re: Broken gnucash-docs (help / it )

xml2po is going to pull all the translatable data out of the xml file and put it in a .pot format. On Fri, Sep 16, 2016 at 10:30 AM, Derek Atkins wrote: > John Ralls writes: > > >> On Sep 15, 2016, at 11:19 AM, Derek Atkins wrote: > >> >

Re: Confirming Action

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… > On Sep 16,

Re: Broken gnucash-docs (help / it )

John Ralls writes: >> On Sep 15, 2016, at 11:19 AM, Derek Atkins wrote: >> >> John, see attached for the full build log. But as Brad points out, it >> looks like there's a reference to a missing file. > > Nope, not a missing file. I finally found it by

Re: Confirming Action

> On Sep 16, 2016, at 8:54 AM, David T. 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

Re: Confirming Action

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

Re: Confirming Action

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

Re: Sorry To Be A Royal Pain...

> On Sep 16, 2016, at 12:50 AM, David T. wrote: > > John, > > Thanks for the time to give me these suggestions. Unfortunately, I kept > hitting snags that would not clear up, and, since my contributions are > sporadic only, I simply nuked the whole environment (again!)

Re: Confirming Action

> On Sep 16, 2016, at 5:43 AM, David T. via gnucash-devel > 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

Confirming Action

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

Re: Sorry To Be A Royal Pain...

John, Thanks for the time to give me these suggestions. Unfortunately, I kept hitting snags that would not clear up, and, since my contributions are sporadic only, I simply nuked the whole environment (again!) and started over. I simply couldn’t get past the “This repository is 27 commits