Home > Archive > PHP Documentation > February 2007 > Re: [PHP-DOC] Shorten subjects of PHPDOC commit emails
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [PHP-DOC] Shorten subjects of PHPDOC commit emails
|
|
| Hannes Magnusson 2007-02-25, 7:00 pm |
| Hi t
On 2/25/07, anatoly techtonik <techtonik@php.net> wrote:
> Hello, everyb.
>
> Is it possible to shorten Subjects of commit emails for PHPDOC?
> To make it easier to see the end of line, i.e. exact file changed.
Why?
Do these 6letters really annoy you that much?
I think it makes sense to print out the module name, then the path and
at last the filename.
This is how all other cvs modules do it, phpdoc should not be any different.
>
> From:
> [PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions feof.xml
> To:
> [PHP-DOC] cvs: /en/reference/filesystem/functions feof.xml
>
> The only confusion could be possible if commits were mailed to
> [PHP-DOC] from different CVS modules, but that is not true.
It is, prefix a commit message with [DOC] and it will get sent here.
-Hannes
>
> t
> --
> --[ http://wiki.phpdoc.info/DocLinks ]--
>
| |
| Philip Olson 2007-02-27, 7:01 pm |
|
>
> You will get your [PHP-DOC] tag anyways. Common - it is a very simple
> and intuitive fix. There is no "useful" information lost over an edge
> case (for what it means). If I am receiving spam like any other user
> on a planet Earth I am against that consistency. =)
I don't see a true need here and would rather not deviate from the
other php mailing lists so prefer to keep the subject line as is.
Get a wider monitor ;)
> You mean this one? - http://beeblex.com/lists/index.php/php.doc.chm/
> 1262?s=
> It is a copy of my post sent to systems@ and there was a follow-up
> thread, but I can't find public archive for systems@, so I can't point
> you to it.
>
> I can rewrite the mail to clearly outline the motivation to separate
> manual editors work from manual tools work. I just afraid the
> explanation will be too banal.
Please write the mail and send it here as a new thread. We'll all
discuss
(again?) then as a group plan how to move forward. If we want this list
then I know we can make it happen but few, except you, even remember
thinking about this topic.
Also, writing down your thoughts will help us all know which list to use
as sometimes there is overlap, like between docweb, phpdoc, and the
newly
proposed list for tools. So three doc lists, will it be (or is it
already)
too confusing? I don't know.
In the future let's discuss these topics here and then post the final
results to systems@ because although our discussions are exciting, they
don't need our spam.
Regards,
Philip
|
|
|
|
|