To be fair, and as I noted in another reply, not often around these parts. But 
I have seen it on other lists. The most likely case would be devs from other 
projects (maybe GTK) getting involved in a discussion on the gnucash-devel list.

However, I see the dev list now has their own tag, which is quite odd since 
I’ve yet to see a developer chime in support of this. The ones I recognize so 
far are all not particularly keen on it.

I sure hope no one posts to both -dev and -user for the same message. What will 
we get when replies start flying from and to each?

Oh, I take that back, I just stopped to check that list, and it seems JohnR 
cross-posts release announcements to both. (And possibly -announce as well) 
Tick-tock...

Regards,
Adrien

> On Apr 10, 2018, at 5:50 PM, Rich Shepard <[email protected]> wrote:
> 
> On Tue, 10 Apr 2018, Adrien Monteleone wrote:
> 
>> I can see how cross-posted messages would turn into tag soup if every list
>> followed this behavior.
> 
> Adrien,
> 
>  Without intending to take the thread onto a different track, how common
> are corss-posted messages? Where are they cross-posted? I've not seen any,
> on any mail list to which I'm subscribed.
> 
> Rich
> _______________________________________________
> gnucash-user mailing list
> [email protected]
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> 


_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to