From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Adding use-package to core Date: Wed, 16 Nov 2022 17:01:37 +0000 Message-ID: <871qq2n89a.fsf@posteo.net> References: <871qq2gbml.fsf@gmail.com> <83o7t6g7w8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34580"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Payas Relekar , stefankangas@gmail.com, johnw@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 16 18:02:22 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 1ovLnq-0008mr-2w for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Nov 2022 18:02:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovLnF-0001o5-Aj; Wed, 16 Nov 2022 12:01:55 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovLnC-0001mE-5j for emacs-devel@gnu.org; Wed, 16 Nov 2022 12:01:42 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovLn9-0006xG-TT for emacs-devel@gnu.org; Wed, 16 Nov 2022 12:01:41 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 3534424008B for ; Wed, 16 Nov 2022 18:01:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1668618098; bh=E83TA8giE501yFgczuH9AoA+iWJl1v/1fPbKJEPABqA=; h=From:To:Cc:Subject:Date:From; b=pT/qKgoSRro2jNBfl3wasDrB7i5BnC8QVTyWSj6xCSblkTLR0q44+RXhCaFjAyIml gFjNQLh+D55ko/xaDRKuiD8FMF1peW08IbcX2b+VqoQhWmpdd0mWOyme4d1NyyqR8J OvnLfwrbVRl9zeRuhsxDIczBq6lrgWvhxAkgFTzjaqps7nYO3yt65oEEjkgzoxPJIW rNIuJ6hkJp5pUs6NxdQ5AbZk7barYy3KSrWv9ZEbB0I239182ajKawTpDZNo2Soc7A fZP+ATRCfnQ0WMj2qJ5tpG7Z3UDFPbs6ZUkk3DujMjXYE5BNcEb5gukWhy/TlgSPIq 5mBVLdsCWOBGA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NC8TX4nLwz9rxW; Wed, 16 Nov 2022 18:01:36 +0100 (CET) In-Reply-To: <83o7t6g7w8.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 16 Nov 2022 18:51:19 +0200") Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_MED=-2.3, 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.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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299955 Archived-At: Eli Zaretskii writes: >> From: Payas Relekar >> Cc: philipk@posteo.net, stefankangas@gmail.com, johnw@gnu.org, >> monnier@iro.umontreal.ca, emacs-devel@gnu.org >> Date: Wed, 16 Nov 2022 20:59:26 +0530 >> >> Eli Zaretskii writes: >> >> >> From: Payas Relekar >> > >> >> Once it is merged and ELPA starts tracking use-package from core, >> >> we should probably ask John to mark the repo as archived on Github as an >> >> added incentive to direct people to emacs-devel as well as prevent >> >> people from creating new bugs/PRs on Github. Does that sound like a good >> >> idea? >> > >> > Yes, I think so. >> >> This is thinking ahead, but we'll want to think about existing open >> issues and PRs before making repo archived. > > I don't understand why. Even if archived, it is accessible, no? AFAIK you cannot respond to an issue on GH when the repository is archived, so that would make it difficult to tackle any issues that would require feedback or discussion in general.