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: [ELPA] new single file package: mpdired.el Date: Fri, 08 Mar 2024 16:34:23 +0000 Message-ID: <875xxwel80.fsf@posteo.net> References: <87o7bpul9s.fsf@ledu-giraud.fr> <87frx158b3.fsf@posteo.net> <878r2tug4b.fsf@ledu-giraud.fr> <877cid55i9.fsf@posteo.net> <87v85wud57.fsf@ledu-giraud.fr> <87ttlg50b4.fsf@posteo.net> <874jdgd72z.fsf@ledu-giraud.fr> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37574"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Manuel Giraud via "Emacs development discussions." To: Manuel Giraud Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Mar 08 17:34:58 2024 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 1ridBR-0009WW-HU for ged-emacs-devel@m.gmane-mx.org; Fri, 08 Mar 2024 17:34:57 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ridB1-0007po-8k; Fri, 08 Mar 2024 11:34:31 -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 1ridAy-0007pN-MP for emacs-devel@gnu.org; Fri, 08 Mar 2024 11:34:28 -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 1ridAw-0003tF-KE for emacs-devel@gnu.org; Fri, 08 Mar 2024 11:34:28 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id E4BBE240027 for ; Fri, 8 Mar 2024 17:34:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1709915664; bh=INXRAPL2O8aVtPAVtdGz6RsCzGRGjowt87LeRLNH0WM=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=lozqp/4fO5vx117LuVcIbbxWBQuzOHhlrw0lTWA8Y6mWzY+Fp2ar1s3Wlx7SEPYnE 5la9wue7igog7+NOSspuCSlDEYpT1eHCfBalDEAP5g8SJiQ/vOkIH4KblolFl9biNq lPrOPgeZXSU4QCW49C0S2jb28FWuWMmOgLU4bfahLq0tvZUrocdrfU2hySUavmvkGJ Zjk79eu1Zp+YnnyNbsUDygvVbjrmBF55PZmpyAhMX7nDe6mwYAq71cPezOSdQDFbbH 1qFf1fuCTEsaMyoM285irGRsnwiyNPGYAK966q/U3cmjnJVG9yEh/PF71UV3m1jrmf Wi+h9Hu+OSXKg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TrsFX27hWz6txP; Fri, 8 Mar 2024 17:34:24 +0100 (CET) In-Reply-To: <874jdgd72z.fsf@ledu-giraud.fr> (Manuel Giraud's message of "Fri, 08 Mar 2024 17:25:08 +0100") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:316918 Archived-At: Manuel Giraud writes: > Philip Kaludercic writes: > > [...] > >>> Ok so it's a "no": I don't want to put a burden on someone else. >> >> Feel free to work on it yourself ;^) I don't think it wouldn't make >> sense, it is just that it seems like a negligible advantage for a rather >> insignificant convenience. I'd also like to be able to track files via >> RCS, but exporting existing files to a Git repository turns out to be >> consistently easier. > > I don't think I'm skilled enough to do this and now that I have just > setup a Git repo I don't think I will be really motivated myself ;-) > > [...] > >>>> As I said, a git forge in that sense is not necessarily needed, you >>>> could also just host the git repository from some website over >>>> https://. >>> >>> Great. I think it is what I would do then. Thanks. >> >> Just keep in mind to enable the "post-update.sample" that invokes "git >> update-server-info", in case you haven't set up a http-Git repo before. >> >> All we need in the end is a URL. > > I fought git hooks a bit but I think I have finally configured it > correctly and the URL is https://ledu-giraud.fr/mpdired.git OK, this works. If you have signed the CA, then you could set the version of your package to some pre-release version, using a ;; Version: 1.0-pre header, and as soon as you are ready to publish just remove the -pre and the package will be automatically published + a new release will be made any time to bump the header. > I'm going to patch with all your previous remarks. Thanks. 1+ -- Philip Kaludercic on peregrine