[development] hook overriding

[Ashraf Amayreh]

IMHO the development mailing list is the best place to point out these
issues and elicit interactions from people who aren't routinely going
through issues all day long, who are not yet aware of that particular issue
or perhaps of drupal's ability to subscribe to them (I didn't know about
that for a very long time).

If issues are not to be discussed on mailing lists, then what exactly do you
propose should be discussed on the development mailing list?

IMHO, mailing lists are pretty well known for being email intensive. A not
totally well formed mail is - in my opinion - much better than having people
thwarted for fear of *clogging* other people's mail boxes. But of course
that's my opinion. Others may disagree.

On 4/11/07, Rob Barreca <rob at electronicinsight.com> wrote:
>
>  Ashraf,
>
> People who are interested in that issue will subscribe to it and get email
> notifications when it is updated. If everyone sent an email to dev when they
> posted/updated an issue we'd all drown in emails. Let's try and keep the
> signal/noise ratio high like Moshe is talking about.
>
> Rob Roy Barreca
> Founder and COO
> Electronic Insight Corporation
> http://www.electronicinsight.com
> rob at electronicinsight.com
>
>
>
> Ashraf Amayreh wrote:
>
> I've just posted two more examples on cases that I believe can't be solved
> without the concept of hook overriding.
>
> http://drupal.org/node/134148
>
> Still opinions on why this feature should (or should not?) be included in
> drupal.
>
> Thanks for your time :-)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070412/2adf21b6/attachment.htm