Tim Hansinger <t...@timhansinger.com> writes: > thank you very much for verifying the issue.
Tim, thank *you* for investigating and fixing the problem! > I am very new to this so I hope this is what you mean. > I created a patch using the patch command [...] Almost there! A Git patch is like the standard Unix patch (which you created), but it includes more information, such as the author, date, and commit message. As to how you do it, you have a couple of options. The original way is to use `git send-mail', where Git creates and sends your patch over e-mail. This is how Linus Torvalds, the author of Git, envisioned Git to be used. A more interactive way is to use Emacs and Magit. First, you pull the Git repo and work on your commit [*]. Then, when you are happy with your commit, you type `W c c' in Magit to create a Git patch file. [*] When crafting your commit, pay attention to the commit message: https://orgmode.org/worg/org-contribute.html#commit-messages P.S. As for testing, I typically do the following: 1. Open `testing/org-test.el' and `M-x eval-buffer RET'. 2. Add some test(s) to `testing/lisp/...'. 3. Evaluate newly added test(s) interactively, using `C-c C-e'. 4. Run all tests with `make test' in the terminal. Rudy -- "All of humanity's problems stem from man's inability to sit quietly in a room alone." --- Blaise Pascal, Pensées, 1670 Rudolf Adamkovič <rud...@adamkovic.org> [he/him] http://adamkovic.org
