From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-repository-version not defined when cloned with mercurial
Date: Sat, 10 Aug 2019 13:44:05 +0300 [thread overview]
Message-ID: <83k1bl8fm2.fsf@gnu.org> (raw)
In-Reply-To: <87zhkh72mk.fsf@mat.ucm.es> (message from Uwe Brauer on Sat, 10 Aug 2019 12:09:55 +0200)
> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Sat, 10 Aug 2019 12:09:55 +0200
>
> > Why not simply ask users who clone into a Mercurial repository to hack
> > up a 'git' shell script that will do what Emacs expects using
> > Mercurial? I mean, this is an unusual situation which we don't have
> > to support too actively. The hash is only important when reporting
> > bugs.
>
> I am not sure I understand your proposal.
The prop[osal is to have a script called 'git' which would call hg to
return the Git hash of a repository cloned with hg. Then Emacs will
get what it wants what it calls "git rev-parse".
> Mercurial can without problems translate between both hashes.
>
> However suppose I run the compiled version for a while (and suppose I
> even have deleted the cloned mercurial repository) and want to
> report a bug, then I don't know for which mercurial I compiled that
> version, and I cannot calculate the corresponding git hash.
AFAIR, the hash is computed when Emacs is built, and is recorded in
the built Emacs. It cannot be calculated after the build.
next prev parent reply other threads:[~2019-08-10 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 15:40 emacs-repository-version not defined when cloned with mercurial Uwe Brauer
2019-08-09 20:24 ` Paul Eggert
2019-08-10 7:52 ` Sven Joachim
2019-08-10 8:35 ` Uwe Brauer
2019-08-10 8:29 ` Uwe Brauer
2019-08-10 9:17 ` Stefan Monnier
2019-08-10 9:54 ` Eli Zaretskii
2019-08-10 10:09 ` Uwe Brauer
2019-08-10 10:44 ` Eli Zaretskii [this message]
2019-08-10 13:12 ` Uwe Brauer
2019-08-10 13:33 ` Eli Zaretskii
2019-08-10 13:58 ` Uwe Brauer
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=83k1bl8fm2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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.