From: Xinglu Chen <public@yoctocell.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 48232@debbugs.gnu.org
Subject: [bug#48232] [PATCH 0/2] Add mercurial-commitsigs and some changes to Mercurial.
Date: Fri, 14 May 2021 13:52:03 +0200 [thread overview]
Message-ID: <8735upzg64.fsf@yoctocell.xyz> (raw)
In-Reply-To: <87k0o3u0wk.fsf@gnu.org>
On Wed, May 12 2021, Ludovic Courtès wrote:
> Perhaps you need to handle the case where HGEXTENSIONPATH is undefined?
> (This could explain the test failures that you see, no?)
That could be the case.
> Also, I’m no Pythonista, but if ‘sys.path’ is a list, then you have to
> split the value of HGEXTENSIONPATH on colons.
Good point, will do that.
next prev parent reply other threads:[~2021-05-14 11:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 20:46 [PATCH 0/2] Add mercurial-commitsigs and some changes to Mercurial Xinglu Chen
2021-05-04 20:56 ` Xinglu Chen
2021-05-04 20:58 ` [bug#48232] " Xinglu Chen
2021-05-11 10:26 ` Ludovic Courtès
2021-05-11 11:27 ` Xinglu Chen
2021-05-11 12:29 ` Ludovic Courtès
2021-05-11 13:17 ` Xinglu Chen
2021-05-12 9:21 ` Xinglu Chen
2021-05-12 20:56 ` Ludovic Courtès
2021-05-14 11:52 ` Xinglu Chen [this message]
2021-05-15 9:17 ` [bug#48232] [PATCH v2 0/2] Add hg-commitsigs " Xinglu Chen
2021-05-15 9:17 ` [bug#48232] [PATCH v2 1/2] gnu: Add hg-commitsigs Xinglu Chen
2021-05-16 21:14 ` Ludovic Courtès
2021-05-16 21:33 ` Xinglu Chen
2021-05-15 9:17 ` [bug#48232] [PATCH v2 2/2] gnu: mercurial: Patch to make it read HGEXTENSIONPATH Xinglu Chen
2021-05-16 21:16 ` Ludovic Courtès
2021-05-17 20:07 ` bug#48232: [PATCH v2 0/2] Add hg-commitsigs and some changes to Mercurial Xinglu Chen
2021-05-04 21:00 ` [bug#48232] [PATCH 1/2] gnu: Add mercurial-commitsigs Xinglu Chen
2021-05-04 21:00 ` [bug#48232] [PATCH 2/2] gnu: mercurial: Add PYTHONPATH to Xinglu Chen
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=8735upzg64.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=48232@debbugs.gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.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.