Re: documentation bug 687820

Op dinsdag 7 februari 2017 18:50:16 CET schreef David T.: > Once again, Geert, you come to clarify. Indeed, I was not aware that this > was a comma-delimited list. With only one dependency, that is not clear > from the page. > > Once again, I prove that there is nothing too simple that I can’t

Re: documentation bug 687820

Once again, Geert, you come to clarify. Indeed, I was not aware that this was a comma-delimited list. With only one dependency, that is not clear from the page. Once again, I prove that there is nothing too simple that I can’t screw up. David > On Feb 7, 2017, at 3:40 PM, Geert Janssens

Re: documentation bug 687820

Op dinsdag 7 februari 2017 10:17:38 CET schreef David T. via gnucash-devel: > Frank, > I'm pretty sure those features are not opened to mere mortals, at least, I > can't see them. That's what I meant when I said I could only edit an > existing dependency entry. David T. > When I open bugs, I

Re: documentation bug 687820

6, 2017 7:53 > PMTo: David Carlson;Frank H. Ellenberger;Cc: > gnucash-devel@gnucash.org;Subject:Re: documentation bug 687820 David, > Frank,I was trying to add the new bug as a dependency of the older > one (as Frank did earlier), but my view only offers an edit option, > which remove

Re: documentation bug 687820

Mon, Feb 6, 2017 7:53 > PMTo: David Carlson;Frank H. Ellenberger;Cc: > gnucash-devel@gnucash.org;Subject:Re: documentation bug 687820 David, > Frank,I was trying to add the new bug as a dependency of the older > one (as Frank did earlier), but my view only offers an edit option, > whi

Re: documentation bug 687820

;Subject:Re: documentation bug 687820 David, Frank,I was trying to add the new bug as a dependency of the older one (as Frank did earlier), but my view only offers an edit option, which removed the earlier dependency. I wanted to keep the earlier dependency to keep the pieces linked, so I changed

Re: documentation bug 687820

ue Feb 07 04:12:29 GMT+05:00 2017 To: "Frank H. Ellenberger" <frank.h.ellenber...@gmail.com> Cc: "gnucash-devel@gnucash.org" <gnucash-devel@gnucash.org> Subject: Re: documentation bug 687820 OK. I did not know about the histroy link, but the See Also reference and th

Re: documentation bug 687820

Now I see in that history that David T removed those changes and I missed those changes. So I am just not up to date. I am curious though, How does one find related bugs if those fields are not used? David C On Mon, Feb 6, 2017 at 5:12 PM, David Carlson wrote: >

Re: documentation bug 687820

OK. I did not know about the histroy link, but the See Also reference and the Depends on changes are not appearing where they are supposed to even if I refresh my view of the bug, Do I have to log out and log back in to refresh my view of the summary box at the top of the bug report? David C

Re: documentation bug 687820

Hi David, Am 06.02.2017 um 23:15 schrieb David Carlson: > David, > > I received two emails from Gnucash saying that you added references to bug > 778254 to bug 687820, but when I opened bug 687820 I could not find those > references. > > FYI. > > David C In the upper right corner behind

documentation bug 687820

David, I received two emails from Gnucash saying that you added references to bug 778254 to bug 687820, but when I opened bug 687820 I could not find those references. FYI. David C ___ gnucash-devel mailing list gnucash-devel@gnucash.org

Moving Forward with Documentation Bug 687820

Hello, Nearly five years ago, I created Bug 687820 in a more innocent time. In that bug, I outlined an ambitious plan to restructure the Tutorial and Concepts Guide, which received a modicum of positive support when I initially submitted it. At this time, I think that I am comfortable