/[smeserver]/rpms/qpsmtpd/sme8/0007-Add-guidelines-for-commit-messages.patch
ViewVC logotype

Annotation of /rpms/qpsmtpd/sme8/0007-Add-guidelines-for-commit-messages.patch

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.1 - (hide annotations) (download)
Sun Nov 14 20:50:20 2010 UTC (13 years, 11 months ago) by slords
Branch: MAIN
CVS Tags: qpsmtpd-0_84-3_el5_sme, qpsmtpd-0_84-6_el5_sme, qpsmtpd-0_84-2_el5_sme, qpsmtpd-0_84-5_el5_sme, qpsmtpd-0_84-8_el5_sme, qpsmtpd-0_84-9_el5_sme, qpsmtpd-0_84-4_el5_sme, qpsmtpd-0_84-7_el5_sme, HEAD
* Sun Nov 14 2010 <slords@mail.com> 0.84-2.sme
- Sync with upstream git repo.
- Fix require_resolvable_fromhost doesn't work [SME: 6369]
- Fix TLS security defaults [SME: 6366]
- Fix fatal errors when mail has no headers [SME: 6345]

1 slords 1.1 From 3939c7bc514acf487f56a4893dbcbb28abbb1ade Mon Sep 17 00:00:00 2001
2     From: Robert <rspier@pobox.com>
3     Date: Mon, 10 May 2010 20:36:54 -0700
4     Subject: Add guidelines for commit messages
5    
6     From git-commit(1)
7     ---
8     docs/development.pod | 11 ++++++++++-
9     1 files changed, 10 insertions(+), 1 deletions(-)
10    
11     diff --git a/docs/development.pod b/docs/development.pod
12     index f991942..0f345e1 100644
13     --- a/docs/development.pod
14     +++ b/docs/development.pod
15     @@ -52,10 +52,19 @@ When you're ready to check it in...
16     git add lib/Qpsmtpd.pm # to let git know you changed the file
17     git add --patch plugin/tls # interactive choose which changes to add
18     git diff --cached # review changes added
19     - git commit
20     + git commit # describe the commit
21     git log -p # review your commit a last time
22     git push origin # to send to github
23    
24     +=head3 Commit Descriptions
25     +
26     +Though not required, it's a good idea to begin the commit message with
27     +a single short (less than 50 character) line summarizing the change,
28     +followed by a blank line and then a more thorough description. Tools
29     +that turn commits into email, for example, use the first line on the
30     +Subject: line and the rest of the commit in the body.
31     +(From: L<git-commit(1)>)
32     +
33     =head3 Submit patches by mail
34    
35     The best way to submit patches to the project is to send them to the
36     --
37     1.7.2.2
38    

admin@koozali.org
ViewVC Help
Powered by ViewVC 1.2.1 RSS 2.0 feed