tinycc-devel
[Top][All Lists]
Advanced

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

Re: [Tinycc-devel] Define __REDIRECT_NTH


From: grischka
Subject: Re: [Tinycc-devel] Define __REDIRECT_NTH
Date: Mon, 13 Sep 2010 17:46:02 +0200
User-agent: Thunderbird 2.0.0.23 (Windows/20090812)

Kirill Smelkov wrote:
On Sun, Sep 12, 2010 at 01:17:07AM +0200, Thomas Preud'homme wrote:
Greeting everybody,

I don't know if I should announce every commit I push to mob but here is another commit.

[...]

Let's maybe add something to "Commit notify - mail to" field at
http://repo.or.cz/editproj.cgi?name=tinycc.git ? (*)

I propose we just add address@hidden as destination for commit
notification mails - this way it would be handy for everyone for keeping
an eye about changes, and also it would be possible to directly discuss
proposed-to-mob commits on the list.

I've only recently thought about activating commit notification.  I don't
have a strong opinion on this, but actually what I'd like to have sometimes
is more background information and not so much the technical detail which
anyway is already present in the commit itself.

For example I'm often curious:  What were people doing when they discovered
bug X or missing feature Y.  What package did they try out on tinycc, what
platform are they working on.  Or with some not quite common feature: why
do we need that, what is it good for.  All such things.  Of course I could
google, but I'm lazy.

In that sense I think some personal notes are a good thing, hence and when.
Not that every single commit needs to be commented on the mailing list.
Nobody wants to be spammed after all ;)  YMMV ...

Other options exist too, of course...

Thanks,
Kirill


(*) Grischka, I forgot admin password (and now I'm not the admin, or
    else I'd directly try it myself :) ), so I cc you too.

(Password sent off list)

As to notifications from repo.or.cz, basically what you would get is this:

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 xyzzz.git.

The branch, mob has been updated
       via  40a8cf3c4192cb6862de14fe8a393324aa655f86 (commit)
      from  ed0fb7ea3538bde77f222b83c6869913e8dc8a59 (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 log (including diffs) follows.

--- grischka




reply via email to

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