aboutsummaryrefslogtreecommitdiff
path: root/mastodon.texi
diff options
context:
space:
mode:
authormarty hiatt <martianhiatus@riseup.net>2023-11-02 11:00:51 +0100
committermarty hiatt <martianhiatus@riseup.net>2023-11-02 11:00:51 +0100
commitd9959ace123b7beb19252819e9b8d92286d40384 (patch)
tree2ae0d786f28db47efc5802f7a7dfa3750fa9191f /mastodon.texi
parentf994ae1b71a8e0b0d4d9c9248e0d55d92e6b3d3e (diff)
update info re patches
Diffstat (limited to 'mastodon.texi')
-rw-r--r--mastodon.texi6
1 files changed, 4 insertions, 2 deletions
diff --git a/mastodon.texi b/mastodon.texi
index 872fb81..b33162d 100644
--- a/mastodon.texi
+++ b/mastodon.texi
@@ -717,6 +717,8 @@ free to open an issue.
PRs, issues, feature requests, and general feedback are very welcome!
+If you prefer emailing patches to the process described below, feel free to send them on. Ideally they'd be patches that can be applied with @samp{git am}, if you want to actually contribute a commit.
+
@menu
* Bug reports::
* Fixes and features::
@@ -737,7 +739,7 @@ in emacs with no init file (i.e. @samp{emacs -q} (instructions and code for doin
this are @uref{https://codeberg.org/martianh/mastodon.el/issues/300, here}) to see if it also happens independently of your own config
(it probably does).
@item
-Enable debug on error (@samp{toggle-debug-on-error}), make the bug happen again,
+Else enable debug on error (@samp{toggle-debug-on-error}), make the bug happen again,
and copy the backtrace that appears.
@item
Open an issue here and explain what is going on. Provide your emacs version and what kind of server your account is on.
@@ -754,7 +756,7 @@ Fork the repository and create a branch off of @samp{develop}.
@item
Run the tests and ensure that your code doesn't break any of them.
@item
-Create a pull request referencing the issue created in step 1.
+Create a pull request (to develop) referencing the issue created in step 1.
@end enumerate
@node Coding style