John,
Thank you for stepping in. This looks much better now, and I believe I
understand it, maybe. I have added a link to this page from the broader
Documentation Update Instructions page (so it won’t be lonely).
David
> On Sep 17, 2018, at 3:04 PM, John Ralls wrote:
>
>
>
>> On Sep 17,
> On Sep 17, 2018, at 10:49 AM, David T. via gnucash-devel
> wrote:
>
> Frank,
>
>> On Sep 17, 2018, at 12:23 PM, Frank H. Ellenberger
>> wrote:
>>
>> Am 17.09.18 um 17:24 schrieb David T.:
>>>
>>> I worked a bit on Build Tools to make the flow seem more natural; see
>>> whether you
David,
Am 17.09.18 um 19:49 schrieb David T.:
> Frank,
>
>> On Sep 17, 2018, at 12:23 PM, Frank H. Ellenberger
>> wrote:
>>
>> Am 17.09.18 um 17:24 schrieb David T.:
>>>
>>> I worked a bit on Build Tools to make the flow seem more natural; see
>>> whether you agree.
>>
>> I am no fan of
Frank,
> On Sep 17, 2018, at 12:23 PM, Frank H. Ellenberger
> wrote:
>
> Am 17.09.18 um 17:24 schrieb David T.:
>>
>> I worked a bit on Build Tools to make the flow seem more natural; see
>> whether you agree.
>
> I am no fan of "__NOTOC__" because I want often send a deep link (read
>
> On Sep 17, 2018, at 8:00 AM, chris graves wrote:
>
> Same thing happens when using the new build to create a new gnucash file.
> Removing the duplicate lines allows the file to open, but they are placed
> right back at the next save.
>
>> On Sep 16, 2018, at 11:56 AM, chris graves
Am 17.09.18 um 17:24 schrieb David T.:
> Frank,
>
>> On Sep 17, 2018, at 10:47 AM, Frank H. Ellenberger
>> wrote:
>>
>> Hi David,
>>
>> Am 17.09.18 um 14:59 schrieb David T.:
>>> Hello,
>>>
>>> Can anyone give me clear language on when and why a documentation creator
>>> would need to reissue
> On Sep 17, 2018, at 8:24 AM, David T. via gnucash-devel
> wrote:
>
> Frank,
>
>> On Sep 17, 2018, at 10:47 AM, Frank H. Ellenberger
>> wrote:
>>
>> Hi David,
>>
>> Am 17.09.18 um 14:59 schrieb David T.:
>>> Hello,
>>>
>>> Can anyone give me clear language on when and why a
Thanks for the background. I wasn’t thinking of the case of other types of
servers, as I so far only deal with Apache.
> On Sep 15, 2018, at 9:28 AM, John Ralls wrote:
>
> If an attacker guesses the path a -Indexes directive won’t stop him from
> requesting the directory from the server. It
David,
I did not see this message previously; it got flagged as spam.
> On Sep 15, 2018, at 6:12 PM, David Cousens wrote:
>
> David
>
> Main reason I pushed it through to the current Help manual is that I had it
> completed to slot in there already apart
> from a bit of minor debugging. If
Frank,
> On Sep 17, 2018, at 10:47 AM, Frank H. Ellenberger
> wrote:
>
> Hi David,
>
> Am 17.09.18 um 14:59 schrieb David T.:
>> Hello,
>>
>> Can anyone give me clear language on when and why a documentation creator
>> would need to reissue the commands in Initializing Documentation Build
Same thing happens when using the new build to create a new gnucash file.
Removing the duplicate lines allows the file to open, but they are placed right
back at the next save.
> On Sep 16, 2018, at 11:56 AM, chris graves wrote:
>
> I performed a git clone of the maint branch on July 31st,
Hi David,
Am 17.09.18 um 14:59 schrieb David T.:
> Hello,
>
> Can anyone give me clear language on when and why a documentation creator
> would need to reissue the commands in Initializing Documentation Build
> Environment? I’d like to clear this issue up on the wiki before it gets lost.
>
>
On Fri, 2018-09-14 at 14:57 -0400, David T. via gnucash-devel wrote:
> Hello,
>
> In the course of another arduous and lengthy thread, the question of
> the Gnome HIG came up. I attach the text in question below.
>
> My question is whether the Guide needs changing at 1.2.1, where it
> says:
>
Hello,
Can anyone give me clear language on when and why a documentation creator would
need to reissue the commands in Initializing Documentation Build Environment?
I’d like to clear this issue up on the wiki before it gets lost.
David
> On Sep 14, 2018, at 10:21 AM, David T. wrote:
>
>
14 matches
Mail list logo
