From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: "If you're still seeing problems, please reopen." [Was: bug#25148:] Date: Fri, 22 Nov 2019 10:16:00 +0000 Message-ID: <871ru0b4in.fsf@gmail.com> References: <20191117113054.49837.qmail@mail.muc.de> <8853390e-f4a5-c295-4f94-cf417ec8db5f@yandex.ru> <83wobv2684.fsf@gnu.org> <878soakddl.fsf@gnus.org> <83wobuzf8y.fsf@gnu.org> <83lfsazbmu.fsf@gnu.org> <83ftiiz57k.fsf@gnu.org> <83sgmhxp1i.fsf@gnu.org> <83mucpxo28.fsf@gnu.org> <83blt5xf08.fsf@gnu.org> <835zjcxucf.fsf@gnu.org> <6b34b5b4-d88e-f4d4-cd54-e3e10dc42279@yandex.ru> <83h82ww9v2.fsf@gnu.org> <878so8b5w6.fsf@gmail.com> <83blt4w7of.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="151786"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: ofv@wanadoo.es, larsi@gnus.org, emacs-devel@gnu.org, rms@gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 22 11:19:19 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iY622-000dHH-SF for ged-emacs-devel@m.gmane.org; Fri, 22 Nov 2019 11:19:19 +0100 Original-Received: from localhost ([::1]:49042 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iY621-00067O-5B for ged-emacs-devel@m.gmane.org; Fri, 22 Nov 2019 05:19:17 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58722) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iY5yz-0004xI-Lb for emacs-devel@gnu.org; Fri, 22 Nov 2019 05:16:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iY5yy-0006He-EY for emacs-devel@gnu.org; Fri, 22 Nov 2019 05:16:09 -0500 Original-Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]:33252) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iY5yw-0006F5-Pj; Fri, 22 Nov 2019 05:16:06 -0500 Original-Received: by mail-wm1-x343.google.com with SMTP id t26so5933220wmi.0; Fri, 22 Nov 2019 02:16:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=BMlEwg30FQY83E5Qqq42LH/iWVN3Smp8pjgbtvgCwi8=; b=ETvkoppZ8kxO8tLtgIEg+gU62FWBNHrsEt/Pym0urZu4F9vvJiqOJGAnYUGgdOS6sD r0048tihv+6HauyTPZrGbX/1ZBeKzvjI1JR8knh3ogw614AMbXBlJ3OloLrSh3vYkdIu qxRIE6D9fjvHK6nBwOkKKzE6vDDapX8aGzi2ryhvClDrzrvzSeUnR4bieDck+ynpcvjL oEVznYrvBLIYRaLVttPIxJ1bZzQFQWo++loIUksOTjWRrf/iTbD5IOITgqNANXKgW4CF xApnlg2EZaUBe6LBO1jQPPlU1lTyKuojghK2N9ybnWt1oqw9Jl7jsrA2G5Q1TnVxTtdy M/UQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=BMlEwg30FQY83E5Qqq42LH/iWVN3Smp8pjgbtvgCwi8=; b=c2b1BZX1Ini94YJKNnNMcswryUorjuxNf9BUiDBPSj18v2VPmCNAcKCwmvJAvNbqru o/dABgsV0SGqGcXwZNl5KCUTW0X0Cgs9N3CyoodZ6/PBZH9ssKkFChE3kqEGwL8u1RL0 fCenCvUzOCj+OrLKSj5WqhGQyXDLRXSFLyDgbwqnLEie1dsJ7XfvVdCQi+MBQfk6W+V5 sr6K5bC5A4qfL60VoDx+hN2PGQMeKgWmK7sjXZLUgkh6PK1Q7EhmkLfM02TqLo0Fif8m 6jeuLUdSH36vun/3+i3ceZDKTdgsH/rbaJ4eSOJdo508m2ZuGZA5CGarGizc27BsQJWm +FEg== X-Gm-Message-State: APjAAAUh0nNFL9v+05Le1OFQ4RCLBk8q0t9daxo2pLCHh9dWvD2QYFJW rj5bNSWsDXkJQ4AM+NkaV+RNq2prKFPnMg== X-Google-Smtp-Source: APXvYqwHL7i+lj8BsY4b0QJBA5xxstr6Gl6iXtauLBBM+H4z2QEbaau8GoGakYov3bfXZNqAgsaLUw== X-Received: by 2002:a1c:9a4f:: with SMTP id c76mr15710868wme.103.1574417764974; Fri, 22 Nov 2019 02:16:04 -0800 (PST) Original-Received: from lolita.yourcompany.com ([2001:818:d820:9500:1ebb:afd8:ab26:f0f6]) by smtp.gmail.com with ESMTPSA id s131sm678648wmf.48.2019.11.22.02.16.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Nov 2019 02:16:04 -0800 (PST) In-Reply-To: <83blt4w7of.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Nov 2019 12:02:08 +0200") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::343 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242615 Archived-At: Eli Zaretskii writes: >> From: Jo=C3=A3o T=C3=A1vora >> Cc: Dmitry Gutov , larsi@gnus.org, ofv@wanadoo.es, >> emacs-devel@gnu.org, rms@gnu.org >> Date: Fri, 22 Nov 2019 09:46:17 +0000 >>=20 >> I think the nice diff output and automatic cross-references, _in the >> Web UI_ are almost guaranteed _not_ to work cross-deployment. But >> from the console it should be exactly the same, yes. > > I still don't think I see the problem. "git diff" works between > branches, and the savannah.nongnu repository will be a copy of the > upstream one. So where's the problem? Maybe there isn't one, and I'm not seeing the full picture. In your scenario, savannah.nongnu is the full-featured fancy-web-enabled GitLab installation where everyone can fork at will, from the Web UI, the console or some other UI. Right? Inside savannah.nongnu, there is an Emacs repo that is a very close copy of our current upstream one. Our current upstream one is insulated from all the frantic JR Hacker business happening in savannah.nongnu. Right? This means, in my limited understanding, that the "Merge pull request" button in the Web UI wouldn't work. Developers have to manually use Git tools to push to, say, git.sv.gnu.org:/srv/git/emacs.git (where our current server lives). The above might be a problem for some, but not me. I think it's pretty minor, actually. And maybe we can convince GitLab to create a feature that automates it, or to enable us to write a plugin, or something. Jo=C3=A3o