will show diffs first for the HEAD version Still for easy lookup:Īn explanation of those conflict markers >. subject='Re: Bug in "revision.Your Q is answered best by alestanis, already. * Reply using the -to, -cc, and -in-reply-to * Save the following mbox file, import it into your mail client,Īvoid top-posting and favor interleaved quoting:
You may reply publicly to this message via plain-text email 1:06 ` Luke Diamand 21:39 ` Ævar Arnfjörð Bjarmason Thread overview: 11+ messages / expand mbox.gz Atom feed top Should at least say "fatal: bad object HEAD in worktree blah" or Other bug (since fixed?), but the error message here is really bad, and Now, obviously the root cause is that the repo is corrupt through some The HEAD revision of some worktrees was corrupt (GitLab creates squash-*ĭoing a "git worktree prune" beforehand makes it work.Įcho 1111111111111111111111111111111111111111 > worktrees/blah/HEAD ("revision.c: -all adds HEAD from all worktrees", ), and that Which is the last release version that doesn't have Duy's d0c39a49cc To "git repack -A -d" a repo on a GitLab server and just got "fatal: badīisect revealed that the reason was that GitLab itself runs 2.14.3, I've also noticed this bug because I tried > error: ssh://whatever/myrepol did not send all necessary objectsĭigging up this old thread. > remote: Total 21 (delta 17), reused 5 (delta 1) > remote: Compressing objects: 100% (20/20), done. > admininstrative information for them would unblock you? > If the latter, I wonder "worktree prune" to remove the > there's nothing important in them (there certainly isn't anymore.).
> In my case I didn't actually want them removed, but fortunately > gc.worktreePruneExpire in git-config(1))," > "DETAILS" below) will eventually be removed automatically (see > "The working tree’s administrative files in the repository (see > git worktree automatically prunes work trees: > them, Git for some reason decided to destroy them." or "I no longer > What do you mean by "expired"? "Even though I want to keep using > error: refs/remotes/origin/master: invalid reflog entry > error: refs/stash: invalid reflog entry > these HEAD refs used by other stale worktrees are pointing at > Am I correct to understand that your "git fsck" would fail because > if it should instead just report something and then keep going. > bails out if there's an error, which I think is the problem. The function other_head_refs() in worktree.c > been GC'd and no longer points to anything sensible > Quite a few of the worktrees have expired - their head revision has > On 15 November 2017 at 22:08, Junio C Hamano wrote: On Thu, Nov 16 2017, Luke Diamand jotted: By adding clear messages to each commit, it is easy for yourself (and others. When we commit, we should always include a message. It is a point in the project you can go back to if you find a bug, or want to make a change. Git considers each commit change point or 'save point'. Subject: Re: Bug in "revision.c: -all adds HEAD from all worktrees" ?ĭate: Mon, 22:39:53 +0100 Adding commits keep track of our progress and changes as we work.
Re: Bug in "revision.c: -all adds HEAD from all worktrees" ? - Ævar Arnfjörð Bjarmason archive mirror help / color / mirror / Atom feed From: "Ævar Arnfjörð Bjarmason"