From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Fetching or installing package dev source from VCS: manual style Date: Tue, 18 Oct 2022 18:04:46 +0300 Message-ID: <831qr518c1.fsf@gnu.org> References: <164484721900.31751.1453162457552427931@vcs2.savannah.gnu.org> <20220214140020.04438C00891@vcs2.savannah.gnu.org> <87bkqmqpvb.fsf@posteo.net> <871qris3xb.fsf@gnus.org> <877d1aqoc1.fsf@posteo.net> <87edvhqdrb.fsf@gnus.org> <871qrh2hh6.fsf@posteo.net> <87mta5oyec.fsf@gnus.org> <87sfjx10x1.fsf@posteo.net> <875ygsp0ng.fsf@gnus.org> <87h70c9bu4.fsf@posteo.net> <874jw73cjy.fsf@posteo.net> <877d0z5216.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5443"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 18 17:13:46 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 1okoHq-00019E-23 for ged-emacs-devel@m.gmane-mx.org; Tue, 18 Oct 2022 17:13:46 +0200 Original-Received: from localhost ([::1]:48292 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1okoHn-0001IV-Hg for ged-emacs-devel@m.gmane-mx.org; Tue, 18 Oct 2022 11:13:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47858) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oko9g-0004gt-59 for emacs-devel@gnu.org; Tue, 18 Oct 2022 11:05:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39670) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oko9d-0004NS-V8; Tue, 18 Oct 2022 11:05:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=lUhEc8epWqVauGjegVzJtjw2xzCEtTahgOc6rz3Zho4=; b=LA5LIcu63uN6 SDiof8sD+LvfQesBVNrbks+wztkklk5rCWGgInJtU9ldV7RnllCS29wZWGfBY7UxP4JRnJVN1Abq5 DxIKiqfq/vJ1JuWBLF1KTtYxjcV40rQ0keRvOIwbej0X7W2dy38c2WdvDKyqje8XDTYp6Lc2H4qdx uLkKQ/NmeODJmwW7csDCqrHkJriquNs3tpocLnbdoz2vrrTkgq2yn6AW2cAMU8jlLUojnuSfTWNCZ CByGLUJHkBs8ISbJ8zRcbvCGF9IlQXtrUUmcESdqWBlYBpg5+PATkVYU6xJlp+XNVxAD6D4ie/hu8 IHfMwyrsGd5H15IpLhFNlg==; Original-Received: from [87.69.77.57] (port=3327 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oko9H-0002Gp-Bn; Tue, 18 Oct 2022 11:05:00 -0400 In-Reply-To: (message from Richard Stallman on Tue, 18 Oct 2022 08:05:29 -0400) 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:298054 Archived-At: > From: Richard Stallman > Cc: emacs-devel@gnu.org > Date: Tue, 18 Oct 2022 08:05:29 -0400 > > > If you have made a change you wish to share > > with the maintainers, first commit your changes then use the command > > @code{package-vc-prepare-patch} to share it. @xref{Preparing Patches}. > > This presumes that a user who suggests a patch to a program will or > should commit that change to some repo in order to email the a patch. > This is an extra step and seems like a gratuitous requirement. It is quite an accepted practice these days. We prefer to get such patches because they are easier to install -- a single command applies the patch and makes a commit with the log message provided with the patch. On the contributor's side, committing is easy, and if the contributor wants, he or she can back out the commit right away, or do it on a scratch branch, or another of the gazillion techniques for that. Or request for "git format-patch" in CONTRIBUTE assumes this workflow.