Moving patches traffic to a another list?
Martin von Zweigbergk
martinvonz at google.com
Thu Mar 26 17:54:10 UTC 2020
On Thu, Mar 26, 2020 at 10:53 AM Augie Fackler <raf at durin42.com> wrote:
>
>
> > On Mar 26, 2020, at 13:44, Pierre-Yves David <
> pierre-yves.david at ens-lyon.org> wrote:
> >
> >
> >
> > On 3/20/20 5:34 PM, Augie Fackler wrote:
> >>> On Mar 20, 2020, at 12:09, Pierre-Yves David <
> pierre-yves.david at ens-lyon.org> wrote:
> >>>
> >>>
> >>>
> >>> On 3/20/20 4:42 PM, Martin von Zweigbergk via Mercurial-devel wrote:
> >>>> On Fri, Mar 20, 2020 at 8:39 AM Pierre-Yves David <
> pierre-yves.david at ens-lyon.org <mailto:pierre-yves.david at ens-lyon.org>>
> wrote:
> >>>> On 3/20/20 4:19 PM, Yuya Nishihara wrote:
> >>>> > unless we're willing to use the mailing list (or plain emails)
> >>>> extensively.
> >>>> That's what I am trying to achieve here :-), more direct
> communication
> >>>> between developers.
> >>>> An alternative for that is to set up a new mercurial-devel-discuss@
> or something and encourage design discussions to go to that list. We
> already have #mercurial also. I don't think the new mailing list would get
> much traffic.
> >>>
> >>> I am -1 on creating a new list for discussion. We have a lot of
> subscribers here that I do not want to loose in the process. The goal is to
> reach out to more people. Not less.
> >> Should we see if we could get only "new patch" mails from phabricator
> sent here, and shove everything else in some other list for archival
> purposes? It sounds like the subject lines are sometimes useful to get
> folks interested in a patch, but the rest is noise...
> >
> >
> > I feel like there are two differents way phabricator gets noisy. First
> there are the cheer number of emails on each diff, that your proposal (of
> sending the initial one on mercurial-devel@) would tackle, However there
> are also the fact that emails in a series are not threaded, so it is harder
> to group them, we can't do mass action on them (like marking a whole thread
> as read/deleted) and the first problem is exacerbated.
> >
> > The proposal to only send the initial patch will make things better, but
> I don't know if they will make them good. I would says "lets give it a try"
> if I know it was technically easy. Keeping in mind the option of taking a
> harder stance later.
>
> Sounds like we can try that. Could you do me a favor and research if this
> is even possible with phabricator? I've got way too much on my plate to
> tackle this in the next couple of weeks.
>
And I suppose those who want the emails should set up Herald rules? Fine
with me.
>
> >
> >> (To be clear: I have no idea if this can be done.)
> >
> > --
> > Pierre-Yves David
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20200326/a07c26a3/attachment-0002.html>
More information about the Mercurial-devel
mailing list