Skip to content

Commit 1773bee

Browse files
committed
Correct capitalization in commit message instructions
1 parent af53db5 commit 1773bee

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

README.org

+2-2
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ be changed using a function, preferably in ~early-init.el~:
189189
*** (D) Commit messages
190190

191191
1. Please theme each package using a separate commit and use commit
192-
messages of the form ~PACKAGE: theme VARIABLE~.
192+
messages of the form ~<package>: Theme <variable>~.
193193

194194
2. If a package has several path variables, then you should theme them
195195
all in one commit.
@@ -198,7 +198,7 @@ be changed using a function, preferably in ~early-init.el~:
198198
use a message such as:
199199

200200
#+begin_src text
201-
foo: theme variables
201+
foo: Theme variables
202202

203203
Theme `foo-config-file', `foo-cache-directory',
204204
and `foo-persistent-file'.

no-littering.el

+3-2
Original file line numberDiff line numberDiff line change
@@ -151,18 +151,19 @@
151151
;;;;; D) Commit messages
152152
;;
153153
;; 1. Please theme each package using a separate commit and use commit
154-
;; messages of the form "<package>: theme <variable".
154+
;; messages of the form "<package>: Theme <variable".
155155
;;
156156
;; 2. If a package has several path variables, then you should theme them
157157
;; all in one commit.
158158
;;
159159
;; 3. If the variable names do not fit nicely on the summary line, then
160160
;; use a message such as:
161161
;;
162-
;; foo: theme variables
162+
;; foo: Theme variables
163163
;;
164164
;; Theme `foo-config-file', `foo-cache-directory',
165165
;; and `foo-persistent-file'.
166+
;;
166167
;; 4. When appropriate add statements like the following to the commit
167168
;; message:
168169
;;

0 commit comments

Comments
 (0)