savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sr #110931] Hide problematic commit on `emacs/nongnu.git`


From: Stefan Monnier
Subject: [sr #110931] Hide problematic commit on `emacs/nongnu.git`
Date: Wed, 6 Sep 2023 17:01:09 -0400 (EDT)

URL:
  <https://savannah.nongnu.org/support/?110931>

                 Summary: Hide problematic commit on `emacs/nongnu.git`
                   Group: Savannah Administration
               Submitter: monnier
               Submitted: Wed 06 Sep 2023 05:01:07 PM EDT
                Category: None
                Priority: 5 - Normal
                Severity: 3 - Normal
                  Status: None
             Assigned to: None
        Originator Email: 
        Operating System: None
             Open/Closed: Open
         Discussion Lock: Any


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 06 Sep 2023 05:01:07 PM EDT By: Stefan Monnier <monnier>
In the `emacs/nongnu.git` repository (more specifically in its
`externals/coffee-mode`, there is an unfortunate commit that triggers Git's
`zeroPaddedFilemode` checks during `fsck`.  Nowadays, Git also performs this
check during `clone`, so when people try to clone `nongnu.git` the `clone`
operation will usuall fail with an error like:

    error: object 2699d230e3b592ae42506d7b5c969a7ac6a4593c:
    zeroPaddedFilemode: contains zero-padded file modes

The usual solution of rewriting this commit is currently impractical, but we
found an alternative which is to hide the offending commit by making that
branch "shallow".

For this reason, we need someone to go on `git.savannah.gnu.org` into the
`emacs/nongnu.git` directory and create a file named `shallow` which contains
the line below:

    b1c16e50e93c662a12c49ac8f18b607656238361

(no space, just hexadecimal characters with a terminating newline).  This
should (according to my tests) have the effect that fetching from that branch
will stop at that revision, thus skipping the next commit (which the one with
the problem) as well as all the subsequent ones.







    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/support/?110931>

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]