emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r99518: * commits: Mention not to mix


From: Glenn Morris
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r99518: * commits: Mention not to mix changes in any given commit.
Date: Wed, 17 Feb 2010 22:18:49 -0800
User-agent: Bazaar (2.0.3)

------------------------------------------------------------
revno: 99518
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Wed 2010-02-17 22:18:49 -0800
message:
  * commits: Mention not to mix changes in any given commit.
modified:
  admin/notes/commits
=== modified file 'admin/notes/commits'
--- a/admin/notes/commits       2010-01-16 20:24:08 +0000
+++ b/admin/notes/commits       2010-02-18 06:18:49 +0000
@@ -1,10 +1,17 @@
 HOW TO COMMIT CHANGES TO EMACS
 
+Most of these points are from:
+
 http://lists.gnu.org/archive/html/emacs-devel/2009-03/msg00555.html
 From:   Miles Bader
 Subject: commit style redux
 Date:   Tue, 31 Mar 2009 12:21:20 +0900
 
+(0) Each commit should correspond to a single change (whether spread
+    over multiple files or not).  Do not mix different changes in the
+    same commit (eg adding a feature in one file, fixing a bug in
+    another should be two commits, not one).
+
 (1) Commit all changed files at once with a single log message (which
     in CVS will result in an identical log message for all committed
     files), not one-by-one.  This is pretty easy using vc-dir now.
@@ -41,6 +48,7 @@
 
 Followup discussion:
 http://lists.gnu.org/archive/html/emacs-devel/2010-01/msg00897.html
+http://lists.gnu.org/archive/html/emacs-devel/2010-02/msg00401.html
 
 
 PREVIOUS GUIDELINES FOR CVS


reply via email to

[Prev in Thread] Current Thread [Next in Thread]