[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs-repository-version not defined when cloned with mercurial

From: Uwe Brauer
Subject: Re: emacs-repository-version not defined when cloned with mercurial
Date: Sat, 10 Aug 2019 10:35:26 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

>>> "SJ" == Sven Joachim <address@hidden> 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: smime.p7s
Description: S/MIME cryptographic signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]