From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: emacs-repository-version not defined when cloned with mercurial
Date: Sat, 10 Aug 2019 10:35:26 +0200 [thread overview]
Message-ID: <8736i9a04x.fsf@mat.ucm.es> (raw)
In-Reply-To: 87ftm9qwx9.fsf@turtle.gmx.de
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
>>> "SJ" == Sven Joachim <svenjoac@gmx.de> writes:
> On 2019-08-09 13:24 -0700, Paul Eggert wrote:
>> On 8/9/19 8:40 AM, Uwe Brauer wrote:
>>> Any change to tell emacs to use the mercurial hash tag?
>>
>> Sorry, it's not clear what you're asking for here. If you'd like to
>> write and debug the feature it sounds like it'd be a good thing to add
>> to Emacs, though I wouldn't expect it to appear unless a
>> Mercurial-using developer takes the initiative to develop it since it
>> should be needed only by developers of Emacs.
> It might actually be a bit confusing to them if mercurial revision IDs
> are included in bug reports, since those do not exist in the git
> repository. And I have not found a way to get the original git SHA1
> back, at least it is not reported in "hg log --debug".
This is possible
1. Short hash: log -r shortHGhash --template '{gitnode|short}\n'
2. Long hash: log -r shortHGhash --template '{gitnode}\n'
Uwe Brauer
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-08-10 8:35 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 [this message]
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
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
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=8736i9a04x.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).