all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Glenn Morris <rgm@gnu.org>, 36534@debbugs.gnu.org
Cc: Valentin Gatien-Baron <valentin.gatienbaron@gmail.com>
Subject: bug#36534: closed (Re: bug#36534: 25.2; mercurial vc-annotate sometimes fails when using the evolve mercurial extension)
Date: Sun, 13 Dec 2020 03:57:12 +0200	[thread overview]
Message-ID: <1d2f084c-6ef1-5086-1deb-18da7cd7ebdd@yandex.ru> (raw)
In-Reply-To: <26k0tmyhvm.fsf@fencepost.gnu.org>

Hi Glenn,

Thanks.

On 12.12.2020 20:54, Glenn Morris wrote:
> 
> Hi, this change causes a test failure.
> 
> Ref eg https://hydra.nixos.org/build/132497145

Apparently Hg shows revision "-1" for a file in a repository with no 
commits at all (which is confirmed by 
https://stackoverflow.com/a/28831490/615245).

I can't reproduce it locally, though. My Hg is 5.3.1, Hydra's is 4.7. 
Apparently that behavior changed at some point, but I can't find the 
exact version and change log entry.

The exact values are not very important for that test, so I'll just add 
another possible one.





      reply	other threads:[~2020-12-13  1:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07  4:55 bug#36534: 25.2; mercurial vc-annotate sometimes fails when using the evolve mercurial extension Valentin Gatien-Baron
2020-11-26 11:56 ` Lars Ingebrigtsen
2020-11-28 18:17   ` Dmitry Gutov
2020-12-02 11:17     ` Andrii Kolomoiets
2020-12-10  0:26       ` Dmitry Gutov
2020-12-10  0:39 ` Dmitry Gutov
     [not found] ` <handler.36534.D36534.160756079129946.notifdone@debbugs.gnu.org>
2020-12-12 18:54   ` bug#36534: closed (Re: bug#36534: 25.2; mercurial vc-annotate sometimes fails when using the evolve mercurial extension) Glenn Morris
2020-12-13  1:57     ` Dmitry Gutov [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1d2f084c-6ef1-5086-1deb-18da7cd7ebdd@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=36534@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    --cc=valentin.gatienbaron@gmail.com \
    /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.