From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: rmsbolt.el [Was: Colorful line numbers] Date: Sat, 23 Jul 2022 13:25:12 -0400 Message-ID: References: <87leslpow2.fsf@gmail.com> <83ilnpl8e0.fsf@gnu.org> <874jz9peq0.fsf@gmail.com> <837d45l6ge.fsf@gnu.org> <87zgh1nyo6.fsf@gmail.com> <831qudl1k3.fsf@gnu.org> <87v8rpntiv.fsf@gmail.com> <83sfmtjjy8.fsf@gnu.org> <87fsitnpxd.fsf@gmail.com> <83k085jgxr.fsf@gnu.org> <87tu77vq1a.fsf@eve> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31091"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: =?windows-1252?B?Sm/jbyBU4XZvcmE=?= , Eli Zaretskii , emacs-devel To: Jay Kamat Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 23 19:26:12 2022 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 1oFItI-0007sK-9I for ged-emacs-devel@m.gmane-mx.org; Sat, 23 Jul 2022 19:26:12 +0200 Original-Received: from localhost ([::1]:34726 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oFItH-0004iM-1H for ged-emacs-devel@m.gmane-mx.org; Sat, 23 Jul 2022 13:26:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42414) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oFIsW-0003x6-6p for emacs-devel@gnu.org; Sat, 23 Jul 2022 13:25:24 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:22530) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oFIsT-0007z0-C1; Sat, 23 Jul 2022 13:25:23 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 4317F44182B; Sat, 23 Jul 2022 13:25:19 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D6AC2441816; Sat, 23 Jul 2022 13:25:13 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1658597113; bh=aEStQrHQQCRMu9RUac234WeScun7lLWfGsdu+1IGXQM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=T77jqTCoENxgf8MOCB9Etw5UfJ6yuexb6Rc3uqw08vrw2sMQ5BfEBcXkgnrn7ne1E qMolok7v/5ekoL9S+sAbGfNA2lxmWbAH7EW2ecjUaVvUiXVveh5JFd1727rRo/iMmh x2ejXRMb83bPJtn7wJmrEO76RnZ2/qeWwfYM53uo7heVTyXjQn4C6X4dpUwJRNydSS yIHwN+OxqGTK1NdUeuheXaH2qY6j3tPloGGpqBbegFuzNvKtKBynlIZpDalE4yHkMb 6hSVlpc87KB616EDiDkIL5SpKSJjvJIxi+gbCNgExjM+Tcbo5beMdweHsdGSuy72Rj lBRt4MU5WGvpA== Original-Received: from pastel (unknown [45.72.195.111]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 986B912016C; Sat, 23 Jul 2022 13:25:13 -0400 (EDT) In-Reply-To: <87tu77vq1a.fsf@eve> (Jay Kamat's message of "Sat, 23 Jul 2022 07:53:37 -0700") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:292547 Archived-At: > I am personally open to putting the package on ELPA (or nongnu ELPA). I just looked at the code's apparent ownership, and it looks like there are a few contributors which would need to sign paperwork before we can add it to GNU ELPA. Would you willing to help get that paperwork done, or do you prefer we put it into NonGNU ELPA? > My main concern is that I would prefer to keep upstream where it is to > avoid moving things around - and ideally I would like to avoid doing > extra work for new versions (melpa automatically builds new versions > every time I push/tag a release). I haven't followed elpa very closely > but my impression is that you might be able to set a remote upstream > but you would need to manually keep re-syncing to keep things up to > date in elpa. Yes, nowadays most GNU ELPA packages are maintained upstream. And there's no need to push to elpa.git, instead we have a cron job that pulls into it (which also means the upstream should *not* force push even if the last push was "just a few minutes ago so surely noone will notice") and a new release is made whenever the `Version:` header is bumped. Stefan