From: "Omar Antolín Camarena" <omar.antolin@gmail.com>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: "Omar Antolín Camarena" <omar.antolin@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
Bastien <bzg@gnu.org>,
"Eric Abrahamsen" <eric@ericabrahamsen.net>,
emacs-devel@gnu.org, "Tim Landscheidt" <tim@tim-landscheidt.de>
Subject: Re: ELPA git repo contains zero-padded file modes and running ~$ make fails
Date: Thu, 01 Feb 2024 17:52:15 -0600 [thread overview]
Message-ID: <87eddvd9ow.fsf@matem.unam.mx> (raw)
In-Reply-To: <87zfwj94i2.fsf@daniel-mendler.de> (Daniel Mendler's message of "Thu, 01 Feb 2024 23:57:57 +0100")
> For example you will create commit 2b2e62af001312a9b97724855855dfec51b5bec6 on Oct 13, 2065.
Correct. I have no idea how that happened either! And I don't know how to keep from happening again. Maybe I'm more prone to the issue because I commit from WSL on Windows and from a VM or Chroot on ChromeOS: I usually have the "outer" Windows or ChromeOS clock visible, but I usually have no idea what time the "inner" Linux environment thinks it is. But still: 1970, 2065? How did that happen and why does it only happen occasionally? But prevention of further instances is not as important as fixing the current problem:
Stefan Monnier mentioned rebasing but I'm unclear on what I am supposed to rebase on what (and I'm also unclear on how that would help: wouldn't the weird commit still be present?). I'll gladly do whatever is necessary to fix the embark repository now, I just don't understand what exactly Stefan proposes I do.
--
Omar
next prev parent reply other threads:[~2024-02-01 23:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 5:57 ELPA git repo contains zero-padded file modes and running ~$ make fails Bastien
2020-05-21 6:08 ` Bastien
2020-05-26 2:19 ` Stefan Monnier
2020-05-26 4:21 ` Eric Abrahamsen
2020-05-31 15:41 ` Bastien
2020-05-31 17:10 ` Stefan Monnier
2020-05-31 20:16 ` Eric Abrahamsen
2020-06-01 7:04 ` Bastien
2020-06-01 17:31 ` Eric Abrahamsen
2020-06-01 7:03 ` Bastien
2020-06-01 13:37 ` Stefan Monnier
2020-06-01 17:09 ` T.V Raman
2020-06-01 23:47 ` Bastien
2024-02-01 15:56 ` Tim Landscheidt
2024-02-01 18:13 ` Stefan Monnier
2024-02-01 19:08 ` Stefan Monnier
2024-02-01 23:11 ` Stefan Kangas
2024-02-02 3:16 ` Stefan Monnier
2024-02-02 3:17 ` Stefan Monnier
2024-02-02 11:01 ` Tim Landscheidt
2024-02-02 13:10 ` Stefan Monnier
2024-02-02 13:30 ` Stefan Monnier
2024-02-02 13:42 ` Emanuel Berg
2024-02-01 21:55 ` Omar Antolín Camarena
2024-02-01 22:57 ` Daniel Mendler via Emacs development discussions.
2024-02-01 23:52 ` Omar Antolín Camarena [this message]
2024-02-02 3:09 ` Stefan Monnier
2024-02-02 4:47 ` chad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eddvd9ow.fsf@matem.unam.mx \
--to=omar.antolin@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=tim@tim-landscheidt.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.