commits 2.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162
  1. HOW TO COMMIT CHANGES TO EMACS
  2. Most of these points are from:
  3. http://lists.gnu.org/archive/html/emacs-devel/2009-03/msg00555.html
  4. From: Miles Bader
  5. Subject: commit style redux
  6. Date: Tue, 31 Mar 2009 12:21:20 +0900
  7. (0) Each commit should correspond to a single change (whether spread
  8. over multiple files or not). Do not mix different changes in the
  9. same commit (eg adding a feature in one file, fixing a bug in
  10. another should be two commits, not one).
  11. (1) Commit all changed files at once with a single log message (which
  12. in CVS will result in an identical log message for all committed
  13. files), not one-by-one. This is pretty easy using vc-dir now.
  14. (2) Make the log message describe the entire changeset, perhaps
  15. including relevant changelog entries (I often don't bother with
  16. the latter if it's a trivial sort of change).
  17. Many modern source-control systems vaguely distinguish the first
  18. line of the log message to use as a short summary for abbreviated
  19. history listing (in arch this was explicitly called the summary,
  20. but many other systems have a similar concept). So it's nice if
  21. you can format the log entry like:
  22. SHORTISH ONE-LINE SUMMARY
  23. MULTIPLE-LINE DETAILED DESCRIPTION POSSIBLY INCLUDING (OR
  24. CONSISTING OF) CHANGELOG ENTRIES
  25. [Even with CVS this style is useful, because web CVS browsing
  26. interfaces often include the first N words of the log message of
  27. the most recent commit as a short "most recent change"
  28. description.]
  29. (3) Don't phrase log messages assuming the filename is known, because
  30. in non-file-oriented systems (everything modern other than CVS),
  31. the log listing tends to be treated as global information, and the
  32. connection with specific files is less explicit.
  33. For instance, currently I often see log messages like "Regenerate";
  34. for modern source-control systems with a global log, it's better to
  35. have something like "Regenerate configure".
  36. Followup discussion:
  37. http://lists.gnu.org/archive/html/emacs-devel/2010-01/msg00897.html
  38. http://lists.gnu.org/archive/html/emacs-devel/2010-02/msg00401.html
  39. PREVIOUS GUIDELINES FOR CVS
  40. For historical interest only, here is the old-style advice for CVS logs:
  41. http://lists.gnu.org/archive/html/emacs-devel/2007-12/msg01208.html
  42. From: Eli Zaretskii
  43. Subject: Re: Log messages in CVS
  44. Date: Sat, 29 Dec 2007 16:06:29 +0200