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 second repo on my computer so I should be able to feed any material to him through that. David suggested I add sections on the other import facilities i.e. DTAUS MT940 and MT942 I'm happy to do that but it will be easier if I can do the changes here then send david a pull request. One problem I will have is getting sample files for the MT940, MT942 and DTAUS formats so I can run through the interfaces. I have a friend who was a manager with Deutsche Bank a few years ago but Klaus is now working for another company in Melbourne. If you know where I can find any sample files I would appreciate getting hold of them. It would be good to have a collection of sample files for testing Gnucash in any case as part of the program. No problem for the internal ones that Gnucash can export. Best wishes David (Cousens) On Tue, 2018-09-18 at 13:15 +0200, Frank H. Ellenberger wrote: > 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 repository github wasn't letting me fork your repository > > separately. It basically told me I already had that repository so no go. I > > could delete my copy of the main Gnucash repository and maybe then it would > > let me do it. > > You can at least pull branches of forks like "BugXXX" in the repo on > your local machine. Usually you do not want to pull the maint and master > branch from forks under the same name. > > I don't know, if it can also be done on the Github Web interface. > Perhaps David T. and Geert should document their progress in the wiki? > > > One other way to do it may be to create the bug branch for the doc update > > in the main Gnucash repository if John and Geert are willing to do that. > > David T. already pulled your work in > https://github.com/Gnucash/gnucash-docs/pull/115/commits > > > something along the lines of the approach in the answer to this may be > > useful. > > https://stackoverflow.com/questions/14865283/proper-git-workflow-scheme-with-multiple-developers-working-on-same-tas > > k. > > > > David Cousens > > Frank > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel