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: Package Eat on NonGNU ELPA diverged Date: Mon, 28 Nov 2022 16:02:36 -0500 Message-ID: References: <87k03evoz8.fsf@disroot.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="8370"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: Akib Azmain Turja Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 28 22:03:36 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 1ozlHq-0001xI-F9 for ged-emacs-devel@m.gmane-mx.org; Mon, 28 Nov 2022 22:03:34 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ozlH5-0003ug-79; Mon, 28 Nov 2022 16:02:49 -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 1ozlGz-0003sh-Or for emacs-devel@gnu.org; Mon, 28 Nov 2022 16:02:41 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ozlGx-0008RN-W3 for emacs-devel@gnu.org; Mon, 28 Nov 2022 16:02:41 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 78AF3804C0; Mon, 28 Nov 2022 16:02:38 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id DD3DC80258; Mon, 28 Nov 2022 16:02:36 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1669669356; bh=HITGNNrxB3ngjfA3YXRVWEDy/1yxFV7J9fiC6q8uMmk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=AZGOi8I9MsU6o2mfRjuev1atl122/TKxl1C6RcW4+AtOUlhOdoAqtwCIYyrCFaHmQ 3XyMU4yPOkJU3v902MyAAe1eVl2b8cDj3VQmTkL7RuQScPgRg1gRPCFlbbqx9RiKA2 /pS9ghE+F9L4NvOlIgNW7bwXWIs91meS4yW6oeDNUXOhBmCGaCDb5A2noLgZmRw/vd OxIY2WqJFGR8hKOhSYTBR5MDdp2pmXyc4bSnWPTmv7knf8x2vE5z1s+jE97vU9iEJ5 TWXZrCkJ12tU1DMFQhWMZUeKJ62lTBV7bVUusKXIt8QHW9M/5dJHvKG2Ed7A+KmWnn RtE+GBzTCH4Fg== Original-Received: from alfajor (unknown [45.44.229.252]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id BD82E120963; Mon, 28 Nov 2022 16:02:36 -0500 (EST) In-Reply-To: <87k03evoz8.fsf@disroot.org> (Akib Azmain Turja's message of "Tue, 29 Nov 2022 01:49:31 +0600") 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 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:300689 Archived-At: > files) and force pushed it. But within that 10-20 minutes, ELPA > machinery fetch from my repository, and now the two repositories > diverged. > > Is there any chance to do something on ELPA side, or do I have to do > something on my side? The problem goes much faster that the `nongnu.git` repository on `git.sv.gnu.org`, because that repository is tracked by several others. Can it be fixed? Yes, technically, but it's a pain in the rear to go and fix them all by hand. It's only justified if there's a *real* problem (like the faulty commit contains something we *really* don't want to keep). Here, we're talking about including a commit with a suboptimal commit message. Nobody will suffer from it, Stefan