On 11/22/12, Jonas Bonn <[email protected]> wrote:

Hi Jonas

> On Tue, 2012-11-20 at 20:43 +0100, Olof Kindgren wrote:
>
>> And most people posting on the lists have no direct
>> connection to OpenCores.
>
> I would probably challenge this assertion... but I really can't be
> bothered at this point.

Well if you're not going to, why mention it?

>
> I'm with Ruben on this, by the way.  The stupidity of having two lists
> with exactly the same content is mind-boggling... why people think they
> also need to post to the second one (the OC one) is beyond me.

That's not something Ruben has said in this thread, at least. I agree,
having 2 lists is annoying because one is redundant (and you can have
someone mount a petty campaign against one of the hosts) and the
sooner we sort this out the better. For the time being we're in a
holding pattern, and we've asked everyone to cross post for the last
year or so.

>
> Just pick a list and post to it, selecting by whatever criteria that
> allows you to sleep at night, and stop posting to both.  If you must
> post to both lists, that's fine, but let's stop harassing people who
> choose not to.

Well, you're asking us to pick sides now. I'd prefer the active
development community at large come to an agreement on which one to
use exclusively if you and the OpenCores boys can't work it out.

Maybe there's something to this, though. Just pick a list you like and
stick to it. Have everyone sign up to both and be done with it. Seems
a shame to split the collaborative work of 10-20 people across 2
lists. The holding pattern continues...

>
> Finally, on the matter of removing recipients when replying to a thread:
> we don't do this!  Use "reply to all" and keep the recipient list intact
> unless you have a _REALLY_ good reason for removing someone.

That's not true - Ruben appears to systematically remove the OpenCores
list from replies.

Cheers

Julius
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc

Reply via email to