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.bugs Subject: bug#60418: [PATCH] Add :vc keyword to use-package Date: Tue, 16 May 2023 19:30:48 +0000 Message-ID: <87zg649iqf.fsf@posteo.net> References: <87zgb6uk2r.fsf@hyperspace> <83ttxd8k1z.fsf@gnu.org> <87v8hrn56l.fsf@hyperspace> <87cz3w2lvb.fsf@posteo.net> <87jzy3ku6u.fsf@hyperspace> <87bkje93ou.fsf@posteo.net> <87y1mhihhy.fsf@hyperspace> <87ildbet2d.fsf@hyperspace> <831qjyoqj5.fsf@gnu.org> <87h6suolt2.fsf@hyperspace> <83ttwun4q4.fsf@gnu.org> <87o7n0fr9e.fsf@hyperspace> <878re3cqro.fsf@posteo.net> <83ild7jq5c.fsf@gnu.org> <87v8h7ba55.fsf@posteo.net> <83zg6ji806.fsf@gnu.org> <87wn1mlmwx.fsf@posteo.net> <83v8h6hb2q.fsf@gnu.org> <87wn1lguqt.fsf@posteo.net> <878re1i70u.fsf@hyperspace> <87cz3cfrr8.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33132"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , felician.nemeth@gmail.com, 60418-done@debbugs.gnu.org, stefankangas@gmail.com To: Tony Zorman Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue May 16 21:31:32 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1pz0OR-0008SZ-Um for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 May 2023 21:31:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pz0OC-0003et-Kp; Tue, 16 May 2023 15:31:16 -0400 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 1pz0Ny-0003bq-R3 for bug-gnu-emacs@gnu.org; Tue, 16 May 2023 15:31:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pz0Ny-0000LN-IM for bug-gnu-emacs@gnu.org; Tue, 16 May 2023 15:31:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pz0Ny-0005xQ-B3 for bug-gnu-emacs@gnu.org; Tue, 16 May 2023 15:31:02 -0400 Resent-From: Philip Kaludercic Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Tue, 16 May 2023 19:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 60418 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Mail-Followup-To: 60418@debbugs.gnu.org, philipk@posteo.net, soliditsallgood@mailbox.org Original-Received: via spool by 60418-done@debbugs.gnu.org id=D60418.168426545822887 (code D ref 60418); Tue, 16 May 2023 19:31:02 +0000 Original-Received: (at 60418-done) by debbugs.gnu.org; 16 May 2023 19:30:58 +0000 Original-Received: from localhost ([127.0.0.1]:48113 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pz0Nu-0005x4-3c for submit@debbugs.gnu.org; Tue, 16 May 2023 15:30:58 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:41205) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pz0Nr-0005wr-AT for 60418-done@debbugs.gnu.org; Tue, 16 May 2023 15:30:56 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id C998A240123 for <60418-done@debbugs.gnu.org>; Tue, 16 May 2023 21:30:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1684265449; bh=5LJXLKFCiBMXRk3oOp2/yj6WzPvpd8znxkXpAKD3HCc=; h=From:To:Cc:Subject:Autocrypt:Date:Message-ID:MIME-Version:From; b=bfnxzzNuXanzbukVTUzKZpF8dyfHg7pGPCuM6u9EOSuxXJwcOoWbaizTUin5y5SWd hfV2CLMsAXqqeMCJfFsC+QPsZAIQrwLb08b7k3LG1/FMbHnVbfgG3744O9RenYFYqZ j/5KVZD7hLUoE52T8DK3Hj5aQIWhtWociZQ69OltsMdusFSlQDFQLZyBj/DoPLxFT8 ez/7U/BukPEigVnW/1M7BSNkRFcVyLRCrz6WcDAUCCQD4rrFAp8tGjQSgaxtghrwpB 1fStMd1TrHwCZniKPP30iBiXGwXiQlVOWMmLhkZI+MKnRTKgKLirqY6K+Y3rjGiC4h FL7rRNqF/5Ljw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QLRD86wYBz9rxH; Tue, 16 May 2023 21:30:48 +0200 (CEST) In-Reply-To: <87cz3cfrr8.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 07 May 2023 10:52:11 +0200") Autocrypt: addr=philipk@posteo.net; keydata= mDMEZBBQQhYJKwYBBAHaRw8BAQdAHJuofBrfqFh12uQu0Yi7mrl525F28eTmwUDflFNmdui0QlBo aWxpcCBLYWx1ZGVyY2ljIChnZW5lcmF0ZWQgYnkgYXV0b2NyeXB0LmVsKSA8cGhpbGlwa0Bwb3N0 ZW8ubmV0PoiWBBMWCAA+FiEEDg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwMFCQHhM4AFCwkI BwIGFQoJCAsCBBYCAwECHgECF4AACgkQ8xYDWXahwulikAEA77hloUiSrXgFkUVJhlKBpLCHUjA0 mWZ9j9w5d08+jVwBAK6c4iGP7j+/PhbkxaEKa4V3MzIl7zJkcNNjHCXmvFcEuDgEZBBQQhIKKwYB BAGXVQEFAQEHQI5NLiLRjZy3OfSt1dhCmFyn+fN/QKELUYQetiaoe+MMAwEIB4h+BBgWCAAmFiEE Dg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwwFCQHhM4AACgkQ8xYDWXahwukm+wEA8cml4JpK NeAu65rg+auKrPOP6TP/4YWRCTIvuYDm0joBALw98AMz7/qMHvSCeU/hw9PL6u6R2EScxtpKnWof z4oM X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:261810 Archived-At: Philip Kaludercic writes: > Tony Zorman writes: > >> On Sat, May 06 2023 18:50, Philip Kaludercic wrote: >>> Eli Zaretskii writes: >>>> I understand that in most cases >>>> users will want to install the latest, >>> >>> I don't know if that is the case. I might be wrong that the revision of >>> the latest release is a good default? Tony, do you think we should add >>> a user-option to regulate this behaviour. >> >> It's certainly my default to install the latest commit of a package >> instead of the latest release. I don't know how general this desire is >> among other people, but an option for controlling the specific behaviour >> sounds great in either case. > > OK, so it might make sense to address this at a later point with a > another patch. > > For now, what issues remain to be resolved before these patches can be > applied? Reviewing the thread, I think everything was ready (aside from a few things that I promised to take care of), so I've pushed the change to master. Thank you for your contribution!