From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Mendler via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: ELPA git repo contains zero-padded file modes and running ~$ make fails Date: Thu, 01 Feb 2024 23:57:57 +0100 Message-ID: <87zfwj94i2.fsf@daniel-mendler.de> References: <87zha1esp6.fsf@gnu.org> <87blmbs4wg.fsf@ericabrahamsen.net> <87imgcxgar.fsf@bzg.fr> <87msskqitp.fsf@vagabond.tim-landscheidt.de> <87il37df3x.fsf@matem.unam.mx> Reply-To: Daniel Mendler Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9161"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Stefan Monnier , Bastien , Eric Abrahamsen , emacs-devel@gnu.org, Tim Landscheidt To: Omar =?utf-8?Q?Antol=C3=ADn?= Camarena Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Feb 01 23:58:53 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 1rVg1F-00028S-0S for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Feb 2024 23:58:53 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rVg0V-0004kt-Uq; Thu, 01 Feb 2024 17:58:07 -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 1rVg0U-0004kd-3G for emacs-devel@gnu.org; Thu, 01 Feb 2024 17:58:06 -0500 Original-Received: from server.qxqx.de ([2a01:4f8:c012:9177::1] helo=mail.qxqx.de) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rVg0R-00041S-43; Thu, 01 Feb 2024 17:58:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=daniel-mendler.de; s=key; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ENwGA1zwaWgZ3VHlvK/npDhpbOljcdyBHcVdJOAqg/M=; b=gMEmsCu7YHT2NzkNOh2gkiD5ZM qLQ3s02cEFy9vuojK1s3kJ5jE7V1k9KH6I3xVjrNO6vj/VHfKwk8cYx9hsCTos4BpMDPGJNIywySX x3ybKWNfXc0nn4/bxcPp0VZxjXgoHq4gHwhMolljnlximqRLQi/mdQQTvKEuUmJm4sOo=; In-Reply-To: <87il37df3x.fsf@matem.unam.mx> ("Omar =?utf-8?Q?Antol=C3=ADn?= Camarena"'s message of "Thu, 01 Feb 2024 15:55:14 -0600") Received-SPF: pass client-ip=2a01:4f8:c012:9177::1; envelope-from=mail@daniel-mendler.de; helo=mail.qxqx.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, SPF_HELO_PASS=-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:315724 Archived-At: Omar Antol=C3=ADn Camarena writes: > I'd be very happy to fix the problem with Embark, of course! But as you k= now, > I'm not very knowledgeable about git. I know neither what I did wrong nor= how to > fix. (I can promise you I did not time travel to 1970 to make a commit.) = Was the > clock on my laptop just wrong when I pushed that commit? More importantly= , how > do I fix this? If I recall correctly it is not the first time that you traveled in time to create an Embark commit. For example you will create commit 2b2e62af001312a9b97724855855dfec51b5bec6 on Oct 13, 2065.