comparison admin/notes/commits @ 107283:396dc65ad74c

Merge from mainline.
author Katsumi Yamaoka <yamaoka@jpl.org>
date Thu, 18 Feb 2010 21:54:17 +0000
parents 68e28bd7d00a 36d0fedf13ca
children
comparison
equal deleted inserted replaced
107282:5937202fb760 107283:396dc65ad74c
1 HOW TO COMMIT CHANGES TO EMACS 1 HOW TO COMMIT CHANGES TO EMACS
2
3 Most of these points are from:
2 4
3 http://lists.gnu.org/archive/html/emacs-devel/2009-03/msg00555.html 5 http://lists.gnu.org/archive/html/emacs-devel/2009-03/msg00555.html
4 From: Miles Bader 6 From: Miles Bader
5 Subject: commit style redux 7 Subject: commit style redux
6 Date: Tue, 31 Mar 2009 12:21:20 +0900 8 Date: Tue, 31 Mar 2009 12:21:20 +0900
9
10 (0) Each commit should correspond to a single change (whether spread
11 over multiple files or not). Do not mix different changes in the
12 same commit (eg adding a feature in one file, fixing a bug in
13 another should be two commits, not one).
7 14
8 (1) Commit all changed files at once with a single log message (which 15 (1) Commit all changed files at once with a single log message (which
9 in CVS will result in an identical log message for all committed 16 in CVS will result in an identical log message for all committed
10 files), not one-by-one. This is pretty easy using vc-dir now. 17 files), not one-by-one. This is pretty easy using vc-dir now.
11 18
39 have something like "Regenerate configure". 46 have something like "Regenerate configure".
40 47
41 48
42 Followup discussion: 49 Followup discussion:
43 http://lists.gnu.org/archive/html/emacs-devel/2010-01/msg00897.html 50 http://lists.gnu.org/archive/html/emacs-devel/2010-01/msg00897.html
51 http://lists.gnu.org/archive/html/emacs-devel/2010-02/msg00401.html
44 52
45 53
46 PREVIOUS GUIDELINES FOR CVS 54 PREVIOUS GUIDELINES FOR CVS
47 55
48 For historical interest only, here is the old-style advice for CVS logs: 56 For historical interest only, here is the old-style advice for CVS logs: