From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Matt Armstrong Newsgroups: gmane.emacs.devel Subject: Re: Concern about new binding. Date: Mon, 08 Feb 2021 09:56:04 -0800 Message-ID: References: <20210202134950.vybbpf3iewbymfjo.ref@Ergus> <20210202134950.vybbpf3iewbymfjo@Ergus> <87zh0mmr54.fsf@gmail.com> <87tuqunw6q.fsf@telefonica.net> <835z3a5miu.fsf@gnu.org> <87pn1f2dlf.fsf@melete.silentflame.com> <87h7mn2122.fsf@melete.silentflame.com> <87mtwfyty6.fsf@melete.silentflame.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37162"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (darwin) Cc: ofv@wanadoo.es, eliz@gnu.org, Richard Stallman , emacs-devel@gnu.org To: Sean Whitton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 08 22:49:08 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l9EP6-0009ZN-9z for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Feb 2021 22:49:08 +0100 Original-Received: from localhost ([::1]:34418 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l9EP5-0003oc-8e for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Feb 2021 16:49:07 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43700) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l9Alf-0004qc-T0 for emacs-devel@gnu.org; Mon, 08 Feb 2021 12:56:11 -0500 Original-Received: from mail-pg1-x52e.google.com ([2607:f8b0:4864:20::52e]:45563) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l9Ald-0003Ts-Px; Mon, 08 Feb 2021 12:56:11 -0500 Original-Received: by mail-pg1-x52e.google.com with SMTP id o21so9311132pgn.12; Mon, 08 Feb 2021 09:56:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=qJo6x0wPeWp2ILiP6PoNXEi0pny5eKp65foJV+Us774=; b=SytV0Map2o+B42LfgwDdatnbYLRIbo9VoFtpUFXegPqnpCQv5VnCTzcdUA9H7rcjxq 3omkSzzkb/l1aJenPjIGpu/yxPOs32XjW7YPDGwgcIIqqlohza5KUrh5iTX7Wg1BlcI0 FBCQQBK2dun/eHFfhAuQH3pQ2dwJL1EY7hmpErUJBxqaVvfwQZwgG/qCH5FQf8iP3Nfk vtttTvuKGIag4up6wJQem0lYpdtpLKlRb4uxkznIQPq/Yb5vjJViD8HWz43bmuFd1YSQ CCkuQhgzVcXrNzM/nInkieOhk0kvGg2+XS/BdU2IYbXvIlftPAc6dT5KCGwKxnabsO0Z YDgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version; bh=qJo6x0wPeWp2ILiP6PoNXEi0pny5eKp65foJV+Us774=; b=HN2cVufgTrJxutuwyafpe3tXiaYMIS9JCVXJho6TPDPSXtQYIzmYXk06S6jyraXLXB y2K6XoXHkbrPGO3ltfo5EsOU3ew2miXmYNWwl9q34JZwEPgVYSJLmenTi7LBCr99Dciq xZSojubVoSJfLxDFUQihXy2/r7Etm+YzqgyjFskws6NP1pG63IRb7Va4wPXhqvqtCKI/ OudxYCZq+Axg2lZXYEgQkbBWjnq0UxUgdZl0thFh6uXyhu9ZNwu4YttF8tZ4K8/AB++p KIfNwSitGYmLqSNdT9GkS4MK8el1B1AUBsMRXsx3AedBBj5k/Qd8YnRaXyARPnVAMmWb QwXA== X-Gm-Message-State: AOAM531aTKycw5fpMxAuoa/8LggVBlGlAWrMXBUPKP42+rG1XZRYL4ZD hrsCkv0BtrA+2ovAQNRnnJ6I2ddwl8O3dw== X-Google-Smtp-Source: ABdhPJzJdNo7eqypkIiUh8QgmpT1Bji+5Db7RKAEF0j6CKxfURToAYm9NElqIBTFCD+Kb8AYVk+jmA== X-Received: by 2002:a63:a804:: with SMTP id o4mr18635460pgf.67.1612806966252; Mon, 08 Feb 2021 09:56:06 -0800 (PST) Original-Received: from matts-mbp-2016.lan (24-113-169-116.wavecable.com. [24.113.169.116]) by smtp.gmail.com with ESMTPSA id b62sm19423544pfg.58.2021.02.08.09.56.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 08 Feb 2021 09:56:05 -0800 (PST) In-Reply-To: <87mtwfyty6.fsf@melete.silentflame.com> (Sean Whitton's message of "Sun, 07 Feb 2021 23:06:25 -0700") Received-SPF: pass client-ip=2607:f8b0:4864:20::52e; envelope-from=gmatta@gmail.com; helo=mail-pg1-x52e.google.com X-Spam_score_int: -14 X-Spam_score: -1.5 X-Spam_bar: - X-Spam_report: (-1.5 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:264182 Archived-At: Sean Whitton writes: > Hello Matt, > > Thank you for your message -- there are however a few misunderstandings > which I'll try to clear up. [...] Thank you for the clarifications. [...] > No, individuals definitely do not require a full local copy of > everything stored in the bug system for nmbug to work. You do need the > git repository containing all the tags, but it is fine to only have > some of the messages (e.g. only recent messages). It may be useful to step away from discussing mechanism, and discuss the problem and use case. The problem statement as I understand it is this: a person wishes to monitor Emacs development by subscribing to emacs-devel. They also wish to know of "interesting" discussions taking place in Emacs bug reports. Today, the practical options are: a) personally subscribe to bug-gnu-emacs and either read every email or write sophisticated filters tuned to their personal interests (this is the "AI" problem). b) rely on the people conducting the bug discussions to move the discussion to emacs-devel when "appropriate." This is a manual process. I don't yet see a consensus that mechanism (b) has been inadequate as a whole, but exploring alternatives can't hurt. > I suggest thinking of the nmbug tagging as independent of debbugs > state, at least to begin with. I think they're mostly solving > different problems. Ok. I see your point and agree. >> Which brings me to: if the point is to make certain kinds of bugs >> more discoverable, adding that feture to debbugs is another option. >> For example, if the bugs tagged "interface change" were interesting, >> debbugs could send updates for such bugs to an "interface change" >> mailing list that interested people could subscribe to. > > Well, you'd have to have debbugs mail the entire bug log to that > mailing list at the point at which it gets tagged, which seems a bit > awkward. The nmbug approach does not involve sending any messages in > order to communicate a tagging of the thread. I don't think debbugs necessarily needs to email the entire history of the bug to emacs-devel. If it simply supported a way to cc'd bug emails from that point forward, to emacs-devel, that could be sufficient to hold the desired discussions in a broader context. A benefit to modifying debbugs is that it is a minimal change to existing workflows. A solution based on notmuch has the drawback that people must use notmuch. I think that may be too much to ask, for too little benefit (in this specific use case -- I think notmuch itself is great).