Hi, Carsten. The new changes are pushed as tehom-html-export-refactor-build-link
I couldn't undo the basing onto tehom-master, try though I might. Something to do with intermediate changes that I couldn't fast-forward and that I probably edited wrong. So I made a separate branch, tehom-html-export-refactor-build-link, which is now pushed to the repo. So tehom-master and html-export-refactor-build-link are already obsolete. I moved the tests into top-level directory testing, as you asked. I'm going to write a separate post describing the test conventions I use. Now a question: IIUC you want a branch that has no tests, that "contains only the changes that would go into org". Since I develop tests and code at about the same time (tests slightly before code), I'm not sure how to arrange the branching in a maintainable way. I could of course make a one-time branch that just removes the testing directory. But then what happens for any future fixes? Seems like each time I'd have to rebase that branch and pick thru changes and make it discard each change that deals with testing/. It seems hard to maintain. Tom Breton (Tehom) _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode