From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Drew DeVault" Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Mon, 30 Aug 2021 08:29:33 +0200 Message-ID: References: <8d0be260-7b15-0b48-42e5-e5a4cc203e54@yandex.ru> <9b839e28-e406-ff4d-0c1e-0bdb9d397f96@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25089"; mail-complaints-to="usenet@ciao.gmane.io" Cc: theo@thornhill.no, Philip Kaludercic , danflscr@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "Dmitry Gutov" , "Lars Ingebrigtsen" , "Eli Zaretskii" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 30 09:06:47 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 1mKbNU-0006GA-Qo for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Aug 2021 09:06:47 +0200 Original-Received: from localhost ([::1]:51856 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mKbNS-0000M6-NX for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Aug 2021 03:06:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47300) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mKane-0005lR-Tw for emacs-devel@gnu.org; Mon, 30 Aug 2021 02:29:45 -0400 Original-Received: from out0.migadu.com ([2001:41d0:2:267::]:19144) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mKand-0002pc-6I; Mon, 30 Aug 2021 02:29:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpwn.com; s=key1; t=1630304977; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=z5/xa1sVXxntKSkqVupxq9Vyl9gxjiittEQXGPk0AJ4=; b=sDTC8UQIWMyyqZT1U24Hzm+NZ31vAjfSy6Cp/D1JU9maDoge1G8TmwJZyfYXLJVQWBcac7 +7RMGab42oPeulksUiQgzjeoVPrrAeDZYEf4WNqz0j33pR4YW/+4/8RfwfMyiCF6wnujyI Jn27dEejsAsOf46xIwmdcHVbQdyW//k9AF1o1mzau1zd2sH10nonWsXBvTw1vi+9eXwIcl 2J7M2Rwv0j31CVw9D5Z5CAsLXA7argJMw3ugvLBraUsX3sN8zMtieqGyC3pA2hDwXToNrP f40+ao00u7R3SB1s+Fn/mv8xpeJOKUaeiI+Fx6hPbzGO70OyAGUBT6grf3JIeg== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: <9b839e28-e406-ff4d-0c1e-0bdb9d397f96@yandex.ru> X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: sir@cmpwn.com Received-SPF: pass client-ip=2001:41d0:2:267::; envelope-from=sir@cmpwn.com; helo=out0.migadu.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham 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:273465 Archived-At: On Mon Aug 30, 2021 at 1:17 AM CEST, Dmitry Gutov wrote: > Consider adopting a "common practice" from the Web UI world: every > discussion (issue/PR/etc) has a unique email address. Every participant > receives messages "From:" a common address (like notifications@sr.ht) > but the Reply-To header includes the unique address which will let the > mail processor on the server associate the reply with the corresponding > thread and resend it to all participants. We cannot add a similar "common practice", as it were, where each message comes From notifications@sr.ht, without breaking DKIM or PGP signatures, which we refuse to do. But, we can track participation in each thread and subscribe users to threads even without a specific email address, by linking up the In-Reply-To chain. This is how I envision your ticket being addressed.