List for cgit developers and users
 help / color / mirror / Atom feed
From: jean-christophe manciot <actionmystique@gmail.com>
To: Christian Hesse <list@eworm.de>
Cc: cgit@lists.zx2c4.com, Christian Hesse <mail@eworm.de>
Subject: Re: [PATCH 1/1] git: update to v2.29.1
Date: Mon, 2 Nov 2020 08:27:40 +0100	[thread overview]
Message-ID: <CAKcFC3byrHx_0Uu7RwbDSM8=8eRBF2DP0MRsh13+NhtmsJNp6A@mail.gmail.com> (raw)
In-Reply-To: <20201101211741.2b77b503@leda>

> Did you run `git submodule update`?

Yes, and I also tried to apply only this 'git: update to v2.29.1'
patch over v1.2.3-8-gadcc4f8 (without the other patches) and it fails
the same way, so all previous patches are not linked to this issue.
This is what I run before building:

# Resetting & cleaning
git reset --hard
git submodule deinit -f .
git submodule update --init
git clean -fxd :/
# Pulling with rebase
git pull -v --progress --rebase
# Updating Submodules
git submodule update --init --recursive
# Fetching Tags
git fetch --tags
# Checking out v1.2.3-8-gadcc4f8
git checkout -f $git_tag

I get this when updating submodules:
Submodule path 'git/sha1collisiondetection': checked out
'855827c583bc30645ba427885caa40c5b81764d2'

I also notice a strange 'warning: unable to rmdir 'git': Directory not
empty' while applying your patch.
--
Jean-Christophe

  reply	other threads:[~2020-11-02  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27  9:42 [PATCH 1/1] git: update to v2.29.1 Christian Hesse
2020-10-31  8:56 ` jean-christophe manciot
2020-10-31  9:20   ` jean-christophe manciot
2020-11-01 20:17   ` Christian Hesse
2020-11-02  7:27     ` jean-christophe manciot [this message]
2020-11-02  8:44       ` jean-christophe manciot
2020-11-02  9:24         ` Christian Hesse
2020-11-04 13:55           ` jean-christophe manciot
2020-11-04 14:10             ` Christian Hesse
2020-11-04 15:05               ` jean-christophe manciot

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='CAKcFC3byrHx_0Uu7RwbDSM8=8eRBF2DP0MRsh13+NhtmsJNp6A@mail.gmail.com' \
    --to=actionmystique@gmail.com \
    --cc=cgit@lists.zx2c4.com \
    --cc=list@eworm.de \
    --cc=mail@eworm.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).