From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51433) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejXUh-0000LF-7T for guix-patches@gnu.org; Wed, 07 Feb 2018 16:43:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ejXUc-0004dY-7t for guix-patches@gnu.org; Wed, 07 Feb 2018 16:43:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:53860) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ejXUc-0004dO-3a for guix-patches@gnu.org; Wed, 07 Feb 2018 16:43:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ejXUb-0004e0-UA for guix-patches@gnu.org; Wed, 07 Feb 2018 16:43:01 -0500 Subject: [bug#30328] [PATCH] gnu: Add emacs-browse-at-remote-gnu. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20180202214457.14147-1-go.wigust@gmail.com> <87k1vq5ec3.fsf@gnu.org> <871shynjzi.fsf@gmail.com> <874lmt17jx.fsf@gnu.org> <877eroycvj.fsf@gmail.com> Date: Wed, 07 Feb 2018 22:41:53 +0100 In-Reply-To: <877eroycvj.fsf@gmail.com> (Oleg Pykhalov's message of "Wed, 07 Feb 2018 19:37:36 +0300") Message-ID: <87eflwzdcu.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Oleg Pykhalov Cc: 30328@debbugs.gnu.org Oleg Pykhalov skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > > >> > What about simply adding the patch to =E2=80=98emacs-browse-at-r= emote=E2=80=99 if > >> > it=E2=80=99s committed upstream way? > >> > >> I'm sorry, what do you mean by =E2=80=9Ccommitted upstream way=E2=80= =9D? > > > > I mean that the patch for Savannah support is already in the reposito= ry > > of =E2=80=98browse-at-remote=E2=80=99, isn=E2=80=99t it? > > Technically it is there. Good. > > Which is to say that the next version of =E2=80=98browse-at-remote=E2= =80=99 will > > have that functionality. > > > > I don=E2=80=99t know, won=E2=80=99t the next =E2=80=98browse-at-remot= e=E2=80=99 include it? > > I hope so, but I cannot answer for them (upstream). Well if it=E2=80=99s already in their repo, let=E2=80=99s assume it=E2=80= =99ll be in the next version. > > The output of =E2=80=98guix lint=E2=80=99 seems to be messy, too. > > Do you mean =E2=80=9Cfilled=E2=80=9D? Sorry for that. Several lines appear to overlap. > So, what will our strategy be? Stay close to upstream by making a new > package with patch or patching the original package? Patch the =E2=80=98emacs-browse-at-remote=E2=80=99 package, I=E2=80=99d say. Sounds good? Thanks, Ludo=E2=80=99.