Hi,

I'm resending this mail to ask for feedback. The previous attempt got side tracked by a discussion on BP/AUDIT and best practices in git.

Below you will find two sample mails as they will be generated from git when changes are pushed to the master repo. The will eventually replace the mails sent by svn as we currently see on gnucash-patches and gnucash-changes.

Can you guys and girls have a look at the mails and let me know what you think of the wording. Too vague ? Too verbose ? To technical ? Just right ?


Thanks.

Geert


--- Begin Message ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "testing".

The branch, master has been updated
       via  d774333d2c7b1c9759054eeddd5d05b57a07a004 (commit)
       via  4807c5abb9b5446b7f24e2bda5a31476e10759ec (commit)
      from  93f930a19515e95e9c48dae48d7230fa79d922cc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d774333d2c7b1c9759054eeddd5d05b57a07a004
Author: Geert Janssens <janssens-ge...@telenet.be>
Date:   Wed Jan 30 15:11:02 2013 +0100

    Change dummy testfile, second commit

commit 4807c5abb9b5446b7f24e2bda5a31476e10759ec
Author: Geert Janssens <janssens-ge...@telenet.be>
Date:   Wed Jan 30 15:10:36 2013 +0100

    Change dummy testfile, first commit

-----------------------------------------------------------------------

Summary of changes:
 testfile.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
testing



--- End Message ---
--- Begin Message ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "testing".

The branch, master has been updated
       via  d774333d2c7b1c9759054eeddd5d05b57a07a004 (commit)
       via  4807c5abb9b5446b7f24e2bda5a31476e10759ec (commit)
      from  93f930a19515e95e9c48dae48d7230fa79d922cc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d774333d2c7b1c9759054eeddd5d05b57a07a004
Author: Geert Janssens <janssens-ge...@telenet.be>
Date:   Wed Jan 30 15:11:02 2013 +0100

    Change dummy testfile, second commit

diff --git a/testfile.txt b/testfile.txt
index b6d7b12..1fc1102 100644
--- a/testfile.txt
+++ b/testfile.txt
@@ -1,4 +1,3 @@
 Dummy test
-Ipsum loret
-More text
+
 Let's just continue to write nonsense, all for a good cause of course ;)

commit 4807c5abb9b5446b7f24e2bda5a31476e10759ec
Author: Geert Janssens <janssens-ge...@telenet.be>
Date:   Wed Jan 30 15:10:36 2013 +0100

    Change dummy testfile, first commit

diff --git a/testfile.txt b/testfile.txt
index 87773b7..b6d7b12 100644
--- a/testfile.txt
+++ b/testfile.txt
@@ -1,3 +1,4 @@
 Dummy test
 Ipsum loret
 More text
+Let's just continue to write nonsense, all for a good cause of course ;)

-----------------------------------------------------------------------

Summary of changes:
 testfile.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
testing



--- End Message ---
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to