From: Gregor Zattler <telegraph@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
Subject: Re: build problem with git worktree linked to main worktree (repo)
Date: Sun, 06 Nov 2022 22:30:45 +0100 [thread overview]
Message-ID: <87fsevsrcq.fsf@no.workgroup> (raw)
In-Reply-To: <jwv8rko68f9.fsf-monnier+emacs@gnu.org>
Hi Stefan, Emacs users,
* Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2022-11-05; 23:59 -04]:
>> The problem arises when the tree from which to build Emacs
>> is actually a linked git worktree as opposed to a fully
>> fletched git repo (main worktree in git parlance).
>
> That's weird. Maybe you could `M-x report-emacs-bug` so someone else
> can look into fixing it?
I filed bug#59064. Actually the problem only exists with
*detached* linked worktrees, linked to a main worktree.
Matt Armstrong found commit 307ad210040 which introduces the
problem. The commit in question was part of Philip
Kaludercic's work to solve Bug#57400, a feature-request for
a vc- command to send patches. He changed
`vc-working-revision' to resolve a hex ID to a symbolic
revision if possible. This will likely be reverted.
As a side-note: I tried to find the offending commit via git
bisect but this hit on the wrong commit
(44ad42240069d8d82772b0c0ef5ec93c2566ca7e).
>> I now will use git worktrees linked to a bare repo.
>
> That's what I've been using for many years, so I can't vouch it'll work
> for everyone, but at least it works well for me.
Thanks for the info.
Ciao; Gregor
--
-... --- .-. . -.. ..--.. ...-.-
prev parent reply other threads:[~2022-11-06 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 23:46 build problem with git worktree linked to main worktree (repo) (was: strange build problem with missing -by.el and -wy.el files) Gregor Zattler
2022-11-06 3:59 ` build problem with git worktree linked to main worktree (repo) Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-06 21:30 ` Gregor Zattler [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsevsrcq.fsf@no.workgroup \
--to=telegraph@gmx.net \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).