David,
Considering David T's expressed concern regarding git, setting up
collaboration in one repo is probably the least complicated. That would allow
you to help out with the more subtle git operations, and allow David T. to
worry less about that part.
Geert
Op dinsdag 18 september 2018 15:2
David,
Doesn’t GitKraken allow you to have multiple remotes in a repo?
Regards,
John Ralls
> On Sep 18, 2018, at 6:00 AM, David Cousens wrote:
>
> Hi Frank,
>
> The problem I was having is that until David Ts changes are merged into the
> main repo
> I can't pull them using either GitHub or
David,
I am glad that you are taking on this aspect of the docs. Thank you.
I would like to note to you (and reiterate for the larger group) the following
important information:
I am a POOR CHOICE to be considered some kind of documentation expert. While I
have a great deal of editorial experi
Hi Frank,
The problem I was having is that until David Ts changes are merged into the
main repo
I can't pull them using either GitHub or GitKraken to my local repo from the
GnuCash-docs github.
I use Gitkraken and it has just allowed me to clone
https://github.com/sunfish62/gnucash-docs into a
Op dinsdag 18 september 2018 10:36:14 CEST schreef David Cousens:
> David,
>
> It was the master branch which was 139 commits behind. I looked at the maint
> branch and noticed it was up to date.
>
> I have tried forking your repository but as I already had a fork of the main
> gnucash-docs repos
Hi David Cousens,
Am 18.09.18 um 10:36 schrieb David Cousens:
> David,
>
> It was the master branch which was 139 commits behind. I looked at the maint
> branch and noticed it was up to date.
>
> I have tried forking your repository but as I already had a fork of the main
> gnucash-docs repo
David,
It was the master branch which was 139 commits behind. I looked at the maint
branch and noticed it was up to date.
I have tried forking your repository but as I already had a fork of the main
gnucash-docs repository github wasn't letting me fork your repository
separately. It basically tol
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 t
David,
I am not sure what is the best way to work on the new documentation with
you. One way fo doing it would be for me to fork your personal repository
into mine. I can then add the changes into your bug branch, push them to my
PR and then create a pull request to your PR to pull the changes i
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 the current vesion of the guide continues for
v3.3 I thought it was worth having it in
the help manual at least. I agree it is really mate
David,
A couple of points.
Why not put this directly into the new chapter in the Guide, rather than into
the Help? This is precisely the kind of detailed information that belongs IMHO
in the Guide rather than Help. I know it’s not in Maint yet, but it will be
shortly.
Next, in the interest of
David ,
I have completed the import section as an addition to the Help manual CH
6. I have put a pull request to gnucash-docs on Github to incorporate it
into maint as the changes for the multiple selection may possibly go into
the next release.
Once it has been pulled into the main Github repo
The typo came about because threw the changes back together quickly before
dinner
I adopted option 1, and it seems to have worked. Not sure how this is any
better.
David
> On Sep 13, 2018, at 8:05 PM, Frank H. Ellenberger
> wrote:
>
> Am 14.09.18 um 00:38 schrieb David T.:
>> Updated as req
Am 14.09.18 um 00:38 schrieb David T.:
> Updated as requested. My commit message includes the full output of "xmllint
> --valid --noout gnucash-guide.xml”
>
> BTW, this sort of experience is yet another example of why I find this
> overall process to be inordinately painful. Some docbook guru
Updated as requested. My commit message includes the full output of "xmllint
--valid --noout gnucash-guide.xml”
BTW, this sort of experience is yet another example of why I find this overall
process to be inordinately painful. Some docbook guru will probably know
immediately why this fails, but
Op donderdag 13 september 2018 14:32:12 CEST schreef D via gnucash-devel:
> Frank,
>
> It's not in my repo because I couldn't get it to compile. To get it to
> compile, I had to incorporate the content of each file into ch_basics.xml.
>
> AFAICT, the new files, ch_importing.xml and ch_configuring
Frank,
It's not in my repo because I couldn't get it to compile. To get it to compile,
I had to incorporate the content of each file into ch_basics.xml.
AFAICT, the new files, ch_importing.xml and ch_configuring.xml, are in my repo,
attached to my bug-796855 branch. So are ch_accts.xml and ch_t
David,
On September 13, 2018, at 1:31 AM, David Cousens
wrote:
>
>> I tried to retain ch_accts.xml and ch_txns.xml in gnucash-guide.xml
>> and simply edit the three files so that
>> they became parts of a single chapter, but this resulted in mysterious
>> “Failure to process entity chapter2”
David,
Am 13.09.2018 um 02:46 schrieb David T. via gnucash-devel:
> I tried to retain ch_accts.xml and ch_txns.xml in gnucash-guide.xml
> and simply edit the three files so that they became parts of a single
> chapter, but this resulted in mysterious “Failure to process entity chapter2”
> error
> I tried to retain ch_accts.xml and ch_txns.xml in gnucash-guide.xml
> and simply edit the three files so that
> they became parts of a single chapter, but this resulted in mysterious
> “Failure to process entity chapter2” errors
> that I was entirely unable to edit away, except by copying the
Hello,
I am sending this message as a heads up that I am preparing a PR for bug
796855, which seeks to pull content from the Help Manual Chapter 3 and put it
into the Guide in Chapter 2.
In the course of doing this, a number of other changes were called for, such
that I needed to add the begi
21 matches
Mail list logo
