FAQ

On 01/24/2012 10:21 AM, Derick Rethans wrote:
Hi,

could something be done about the commit spam subjects? It was
mightly useful to have the paths and the commit messages in there.
The problem here is that you can push multiple changesets at once and
the header will get very long. Max subject length are arbitrary.

I understand that it's useful, so you suggested having a mail for each
commit instead of each push. I prefer mails per push as they are the
only documentation of who pushed what. In case someone pulls from a
person that doesn't have karma and pushes it, I want to ask that
person why and what. So the pushmails is useful for me and gives me a
good overview over the overall change.

So the option is to
(1) have commit mails or push mails only.
(2) both
(3) send one type of mail to a separate mailinglist
(4) change the pushmail format to something useful.

- - dsp
cheers, Derick

On Mon, 23 Jan 2012, rasmus@php.net wrote:

The branch, master on web/master.git has been updated from
4fe64dfdc12c4bd8965ba4af73b900a545a012fb (commit) to
8181453dbb6b46b5da50cf744643c6d1380e97f0 (commit)

http://git.php.net/?p=web/master.git;a=log;h=8181453dbb6b46b5da50cf744643c6d1380e97f0;hp=4fe64dfdc12c4bd8965ba4af73b900a545a012fb

Summary of changes:
scripts/update-user-notes | 19 +++++++++++++++---- 1 files
changed, 15 insertions(+), 4 deletions(-)

-- Log ---------------------------------------- commit
8181453dbb6b46b5da50cf744643c6d1380e97f0 Author: Rasmus Lerdorf
<rasmus@php.net> Date: Mon Jan 23 18:47:00 2012 -0800

No ssl stream on the ancient rsync box, so fake it

diff --git a/scripts/update-user-notes
b/scripts/update-user-notes index ef90da3..64ac120 100755 ---
a/scripts/update-user-notes +++ b/scripts/update-user-notes @@
-20,11 +20,22 @@ if (substr($root,-1) != '/') { } $since =
$argv[2];

+$SSL_fopen = false; +if(in_array('https',
stream_get_wrappers())) { + $SSL_fopen = true; +} + /* get
user notes */ -$fp = @fopen( -
"https://master.php.net/fetch/user-notes.php?token=$token".($since?"&since=$since":""),
- - "r"
-); +if($SSL_fopen) { + $fp = @fopen( +
"https://master.php.net/fetch/user-notes.php?token=$token".($since?"&since=$since":""),
+ "r"
+ ); +} else { + $url =
escapeshellarg("https://master.php.net/fetch/user-notes.php?token=$token".($since?"&since=$since":""));
+ $fp = popen("curl -s $url",'r');
+} + if (!$fp) { exit(1); }

Thank you for your contribution.

Search Discussions

  • Michael Wallner at Jan 25, 2012 at 7:10 pm

    On Tue, 24 Jan 2012 20:33:10 +0100, David Soria Parra wrote:


    I understand that it's useful, so you suggested having a mail for each
    commit instead of each push. I prefer mails per push as they are the
    only documentation of who pushed what. In case someone pulls from a
    person that doesn't have karma and pushes it, I want to ask that person
    why and what. So the pushmails is useful for me and gives me a good
    overview over the overall change.

    So the option is to
    (1) have commit mails or push mails only.
    (2) both (3) send one type of mail to a separate mailinglist (4) change
    the pushmail format to something useful.
    How about a push mail with commit mails referencing the push mail
    following?

    Might look like the following then:

    [ ]-- push mail
    -- mail for commit 1
    -- mail for commit 2
    ...


    Regards,
    Mike
  • David Soria Parra at Jan 26, 2012 at 8:32 am

    On 2012-01-25, Michael Wallner wrote:
    On Tue, 24 Jan 2012 20:33:10 +0100, David Soria Parra wrote:


    I understand that it's useful, so you suggested having a mail for each
    commit instead of each push. I prefer mails per push as they are the
    only documentation of who pushed what. In case someone pulls from a
    person that doesn't have karma and pushes it, I want to ask that person
    why and what. So the pushmails is useful for me and gives me a good
    overview over the overall change.

    So the option is to
    (1) have commit mails or push mails only.
    (2) both (3) send one type of mail to a separate mailinglist (4) change
    the pushmail format to something useful.
    How about a push mail with commit mails referencing the push mail
    following?

    Might look like the following then:

    [ ]-- push mail
    -- mail for commit 1
    -- mail for commit 2
    ...
    I quiet like that option!

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupphp-internals @
categoriesphp
postedJan 24, '12 at 7:34p
activeJan 26, '12 at 8:32a
posts3
users3
websitephp.net

People

Translate

site design / logo © 2022 Grokbase