aboutsummaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2020-01-01 16:05:11 +0100
committerLudovic Courtès <ludo@gnu.org>2020-01-09 23:33:04 +0100
commita7bde77d247ed0765f5378779d67b4668c5d7648 (patch)
tree3fb484bc44e0d296e45ed2562b455ee3148f50cb /HACKING
parentf75243e17e3ff88582314bcb8450e654bb0b556b (diff)
downloadpatches-a7bde77d247ed0765f5378779d67b4668c5d7648.tar
patches-a7bde77d247ed0765f5378779d67b4668c5d7648.tar.gz
doc: Add "Tracking Bugs and Patches" section.
* doc/contributing.texi (Tracking Bugs and Patches): New section. (Submitting Patches): Refer to it. * doc/guix.texi: Update copyright line. * HACKING (Using emacs-debbugs): Remove.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING9
1 files changed, 0 insertions, 9 deletions
diff --git a/HACKING b/HACKING
index 2f0f93f896..deb41a9cef 100644
--- a/HACKING
+++ b/HACKING
@@ -63,12 +63,3 @@ after two weeks, and if you’re confident, it’s OK to commit.
That last part is subject to being adjusted, allowing individuals to commit
directly on non-controversial changes on parts they’re familiar with.
-
-* Using emacs-debbugs
-
-Bug reports and patches are tracked using debbugs. If you are on emacs, you
-can use emacs-debbugs.
-
-List all open bug reports on guix-patches with
-
-C-u M-x debbugs-gnu <RET> <RET> guix-patches <RET> n y