To echo one part of John's comment, I recommend that any description of this
process belongs in the Guide, and not the Help or on the wiki. Since chapter 3
of the Guide is called "Importing into Gnucash," I would probably suggest to
put it there.
David T.
On Wed, Aug 14, 2019 at 8:56, Jo
> On Aug 13, 2019, at 6:25 PM, David Cousens wrote:
>
> At present the transaction importing documentation in the Help manual has no
> full description of how the import main matcher goes about the process of
> searching for and matching an imported transaction to an existing
> transaction or
> On Aug 13, 2019, at 2:54 PM, Christian Gruber
> wrote:
>
> Am 13.08.19 um 02:45 schrieb John Ralls:
>>
>>> On Aug 12, 2019, at 3:12 PM, Christian Gruber
>>> wrote:
>>>
>>> Following my previous thread "[GNC-dev] Contribute to GnuCash development"
>>> I opened a new topic thread about r
Hi David,
Am Mi., 14. Aug. 2019 um 03:26 Uhr schrieb David Cousens
:
>
> At present the transaction importing documentation in the Help manual has no
> full description of how the import main matcher goes about the process of
> searching for and matching an imported transaction to an existing
> tr
At present the transaction importing documentation in the Help manual has no
full description of how the import main matcher goes about the process of
searching for and matching an imported transaction to an existing
transaction or how it assigns a transfer account using the original mapping
proces
Am 13.08.19 um 02:45 schrieb John Ralls:
On Aug 12, 2019, at 3:12 PM, Christian Gruber
wrote:
Following my previous thread "[GNC-dev] Contribute to GnuCash development" I
opened a new topic thread about reworking GoogleTest integration.
At first some investigation results on bug 797344
<
> On Aug 13, 2019, at 9:14 AM, Derek Atkins wrote:
>
> Hi,
>
> On Tue, August 13, 2019 12:03 pm, John Ralls wrote:
>>
>> Yay! I've been asking for you to clean up the old Windows builds for
>> years! Now for a little preventive medicine: take a few minutes to add a
>> cron job.
>
> eTooLazy
Hi,
On Tue, August 13, 2019 3:01 pm, Frank H. Ellenberger wrote:
> Hi,
>
> Am Di., 13. Aug. 2019 um 18:15 Uhr schrieb Derek Atkins :
> :
>> > Flatpak builds should follow the same logic as Windows builds.
>> > Incidentally I like the way that you've separated the flatpack build
>> logs.
>>
>> This
Hi,
Am Di., 13. Aug. 2019 um 18:15 Uhr schrieb Derek Atkins :
:
> > Flatpak builds should follow the same logic as Windows builds.
> > Incidentally I like the way that you've separated the flatpack build logs.
>
> This wasn't me; this was how the build scripts were written.
>
> > There don't seem
Hi,
On Tue, August 13, 2019 12:03 pm, John Ralls wrote:
>
> Yay! I've been asking for you to clean up the old Windows builds for
> years! Now for a little preventive medicine: take a few minutes to add a
> cron job.
eTooLazy. ;)
Writing and testing the script would take more time than just goin
> On Aug 13, 2019, at 7:22 AM, Derek Atkins wrote:
>
> Hi,
>
> Code's /home got to be 91% full (177GB used). So I started looking at
> the data hogs. The #1 hog was Win32 builds.
>
> I cleaned out all interim (non-release) builds for 2.4, 2.6, 3-pre, and
> maint builds from 2018. This red
Hi,
Code's /home got to be 91% full (177GB used). So I started looking at
the data hogs. The #1 hog was Win32 builds.
I cleaned out all interim (non-release) builds for 2.4, 2.6, 3-pre, and
maint builds from 2018. This reduced us down to 89GB used, so now
there are only 30GB of win32 data rema
12 matches
Mail list logo
