summaryrefslogtreecommitdiff
path: root/CONTRIBUTE
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2016-05-24 19:06:20 +0300
committerEli Zaretskii <eliz@gnu.org>2016-05-24 19:06:20 +0300
commit503e752c4a4ec4dc05c112ae82753b85594c99be (patch)
tree65baf0b42077df859f21787584717e41267b6ba4 /CONTRIBUTE
parentfbfd4787fbec11fe69f5e661e7c5ab4436f7cb72 (diff)
downloademacs-503e752c4a4ec4dc05c112ae82753b85594c99be.tar.gz
; * CONTRIBUTE: Fix a typo.
Diffstat (limited to 'CONTRIBUTE')
-rw-r--r--CONTRIBUTE2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTE b/CONTRIBUTE
index 5102b4fe4f1..a70682f29ab 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -183,7 +183,7 @@ intended for more-conservative changes such as bug fixes. Typically,
collective development is active on the master branch and possibly on
the current release branch. Periodically, the current release branch
is merged into the master, using the gitmerge function described in
-admin/notes-git-workflow.
+admin/notes/git-workflow.
If you are fixing a bug that exists in the current release, be sure to
commit it to the release branch; it will be merged to the master