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: Sun, 29 Aug 2021 09:42:14 +0200 Message-ID: References: <8d0be260-7b15-0b48-42e5-e5a4cc203e54@yandex.ru> <837dg4n1ix.fsf@gnu.org> 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="746"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, danflscr@gmail.com, theo@thornhill.no, emacs-devel@gnu.org, monnier@iro.umontreal.ca, dgutov@yandex.ru, larsi@gnus.org To: "Eli Zaretskii" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 29 09:43:20 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 1mKFTL-000AZo-D4 for ged-emacs-devel@m.gmane-mx.org; Sun, 29 Aug 2021 09:43:20 +0200 Original-Received: from localhost ([::1]:55384 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mKFTJ-0000xt-NQ for ged-emacs-devel@m.gmane-mx.org; Sun, 29 Aug 2021 03:43:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50666) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mKFSR-0000Ef-Lp for emacs-devel@gnu.org; Sun, 29 Aug 2021 03:42:23 -0400 Original-Received: from out2.migadu.com ([188.165.223.204]:17437) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mKFSM-0008NV-Ve; Sun, 29 Aug 2021 03:42:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpwn.com; s=key1; t=1630222935; 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=K9bcRJuoZRVJF07aotidqws1qXbZf0WKKhv7LwW6hco=; b=rgpdTmjOBUAfT6OmCflLrLOQw5OmhInu4BrMqbgcFF5KLKizjCCEbSunAw0HClpH4wjBjt NEoOE39LPJgYzh9AHzilicFtIpQJSSMT3bsEgkjNnMruJ2gFmSqv0a+fToeUcpYHd+9Mub xGNACDpnoTnvi85Ppu1qZbv5pUJFv/UvPh2buBr+CD3moy5Tjx3HIrVsxw1PitfO0OI7VK T+1yy7EoEaO2ili7J7oKPLjto8zPgsq1cuPLNuukq6DJ5f9I5Z+JjkjZElCUZTMnqH9eaQ 4VtvwOe+yCzB/WkTC+OISBSkAi7XL4Cu7D73eeMWgeDXlnDVD2HmqjIKm3HLcQ== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: <837dg4n1ix.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: sir@cmpwn.com Received-SPF: pass client-ip=188.165.223.204; envelope-from=sir@cmpwn.com; helo=out2.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_MSPIKE_H2=-0.001, 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:273380 Archived-At: On Sun Aug 29, 2021 at 9:38 AM CEST, Eli Zaretskii wrote: > Rebasing is not just intimidating, it has real problems as well. One > problem that particularly bothers us is that it could, in some > circumstances, cause the same commit to be present more than once. > > I find a hard requirement to use rebase to be user-unfriendly, because > some of us simply don't want to rebase, for reasons of preserving the > original history of the development. Is rebasing really a requirement > in SourceHut? No, it's not a requirement. It's just something I think is a good idea. How do you end up with the same commit twice? > > It depends on all of the participants Cc'ing you. It is common practice > > to "reply all" on mailing lists for this reason. > > Too many people forget to "Reply All", we have this all the time on > our current bug tracker. Is there a way to arrange for automatic > subscription to a discussion once you post to that discussion? This is probably something which can be done. Can you file a ticket? Send an email to ~sircmpwn/lists.sr.ht@todo.sr.ht with the title in the subject line and the body as markdown. > > In a sense. Because you don't have to subscribe to the mailing list to > > participate in a thread, you won't get emails unless the sender has Cc'= d > > you. But you cannot stop them from Cc'ing you, and neither can we, > > unless you ask nicely - which is not a software solution. Such emails > > are not relayed by our mail servers, so it's out of our control. > >=20 > > Subscribing to individual threads is also prioritized. > > Does this mean that currently starting a discussion doesn't > automatically subscribe me to that discussion? Yep. See previous answer.