Summary: Let's do it. However, I prefer doc-cvs@ and doc-bugs@ but
keep phpdoc@ for historical reasons even though it would be nice to
change it to doc@ including the cvs module name. Still thinking about
that one... what does everyone else think?
I don't think renaming phpdoc@ to doc@ is suc
On 8/25/07, Philip Olson <[EMAIL PROTECTED]> wrote:
> > This question has been raised few times but no actions taken yet...
> >
> > If nobody objects I would like* to split this mailing list up into:
> > - phpdoc-cvs@
> >Containing all the CVS commits
> > - phpdoc-bugs@
> >Gets all the
This question has been raised few times but no actions taken yet...
If nobody objects I would like* to split this mailing list up into:
- phpdoc-cvs@
Containing all the CVS commits
- phpdoc-bugs@
Gets all the mails from the bug tracker
- phpdoc@
The day-to-day communication
There
Hannes Magnusson wrote:
> In fact, you mark replies to CVS commits as read automatically with
> this rule so you never notice if anyone replies to it :)
No as long as e-mail client used for reply uses Re: ;-).
Jakub Vrana
On 8/17/07, Jakub Vrana <[EMAIL PROTECTED]> wrote:
> Hannes Magnusson wrote:
> > That would give the people who only want to work on the tools an
> > opportunity to keep track of what is going on there without the
> > "noise" of manual commits.
>
> I automatically mark the manual commits and bug re
Hannes Magnusson wrote:
> That would give the people who only want to work on the tools an
> opportunity to keep track of what is going on there without the
> "noise" of manual commits.
I automatically mark the manual commits and bug reports (alongside my
own messages) as read in my .procmailrc wi
Hello all
This question has been raised few times but no actions taken yet...
If nobody objects I would like* to split this mailing list up into:
- phpdoc-cvs@
Containing all the CVS commits
- phpdoc-bugs@
Gets all the mails from the bug tracker
- phpdoc@
The day-to-day communicati
