From: Tim Landscheidt <tim@tim-landscheidt.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Stefan Kangas" <stefankangas@gmail.com>,
"Omar Antolín Camarena" <omar.antolin@gmail.com>,
Bastien <bzg@gnu.org>,
"Eric Abrahamsen" <eric@ericabrahamsen.net>,
emacs-devel@gnu.org
Subject: Re: ELPA git repo contains zero-padded file modes and running ~$ make fails
Date: Fri, 02 Feb 2024 11:01:22 +0000 [thread overview]
Message-ID: <87le836sfx.fsf@vagabond.tim-landscheidt.de> (raw)
In-Reply-To: <jwvplxf7e9i.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 01 Feb 2024 22:16:33 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> […]
>> Is there something we could add to our scripts to avoid this from
>> happening in the future? I'm thinking of adding a `git fsck` to our
>> scripts before pushing a branch to Savannah, or something. Not sure
>> what's needed.
> We already have:
> [transfer]
> fsckObjects = true
> in the `.gitconfig` of the thingy doing the mirroring of
> upstream branches. But apparently it didn't catch those badDateOverflow
> issues (apparently they're not checked in a systematic fashion?).
But this configuration does not apply to the Git "server"
accepting pushes to ELPA branches where the error that
started this thread occurred, does it?
To accomplish this, I assume something in the Savannah-
sphere needs to be changed. (Though I don't understand why
receive.fsckObjects=true is not the Git default.)
Tim
next prev parent reply other threads:[~2024-02-02 11:01 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 [this message]
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
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=87le836sfx.fsf@vagabond.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=monnier@iro.umontreal.ca \
--cc=omar.antolin@gmail.com \
--cc=stefankangas@gmail.com \
/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.